Bug 535595 (RHQ-2274) - JMX Plugin: format Initial Size and Maximum Size traits in a more user friendly way
Summary: JMX Plugin: format Initial Size and Maximum Size traits in a more user friend...
Keywords:
Status: CLOSED WONTFIX
Alias: RHQ-2274
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 1.2
Hardware: All
OS: All
low
medium
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL: http://jira.rhq-project.org/browse/RH...
Whiteboard:
Depends On:
Blocks: rhq_triage
TreeView+ depends on / blocked
 
Reported: 2009-07-28 21:18 UTC by Ian Springer
Modified: 2014-05-09 15:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-09 15:04:02 UTC
Embargoed:


Attachments (Terms of Use)

Description Ian Springer 2009-07-28 21:18:00 UTC
Currently these two traits have values like the following:

Initial Size:  104857600
Maximum Size: 209715200

We should change them to:

Initial Size:  104,857,600 bytes
Maximum Size: 209,715,200 bytes

or even better:

Initial Size:  100.0 MB
Maximum Size: 200.0 MB


Comment 1 Red Hat Bugzilla 2009-11-10 21:01:17 UTC
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2274


Comment 2 wes hayutin 2010-02-16 16:56:56 UTC
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug

Comment 3 wes hayutin 2010-02-16 17:02:07 UTC
making sure we're not missing any bugs in rhq_triage

Comment 4 Joseph Marques 2010-11-17 17:31:33 UTC
ian, do traits have units?  if not, that's the problem, because all traits are presumed to be strings, and thus don't have an associated formatter.  i suppose adding a new units field for traits would be forward compatible, so that's always an option.

Comment 5 Ian Springer 2010-11-17 17:41:37 UTC
No, they don't. We could either go that route, or for a quick one-off fix, have the plugin do the formatting of those two traits itself.


Note You need to log in before you can comment on or make changes to this bug.