Bug 818683 - write tests that verify the metadata update code supports changing a ResourceType's category from SERVER to SERVICE or from SERVICE to SERVER
Summary: write tests that verify the metadata update code supports changing a Resource...
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Core Server
Version: 4.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-03 18:03 UTC by Ian Springer
Modified: 2024-03-04 13:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 810342 0 medium CLOSED change Resource category of server Resources that should be services from SERVER to SERVICE 2021-02-22 00:41:40 UTC

Internal Links: 810342

Description Ian Springer 2012-05-03 18:03:00 UTC 
The support for changing a type's category was added as part of bug 810342. We just need to write some automated tests for this functionality.
Comment 1 Mike Foley 2012-05-08 19:33:39 UTC 
per BZ triage ... crouch, loleary, foley
Comment 3 Charles Crouch 2012-08-02 20:15:12 UTC 
Unassigning from Ian. Since there isn't anywhere in the product that actually takes advantage of this feature, my suggestion is to have target this at master and have the tests added for RHQ4.5
Comment 4 Charles Crouch 2012-08-29 16:09:50 UTC 
As per 8/20 triage 8/20 pushing to JON312
Comment 5 mark yarborough 2012-11-20 20:46:00 UTC 
Per triage with loleary, crouch, mfoley: Move to JBoss ON product, set target release JON 3.2, clear priority (will be subject to further triage in JON 3.2 timeframe).
Comment 6 Larry O'Leary 2012-11-21 22:55:31 UTC 
As per comment 3, re-targeted to RHQ 4.6 as this in not JBoss ON specific.
Comment 8 Jay Shaughnessy 2013-09-12 15:54:27 UTC 
Unassigning target release for future triage.
Note You need to log in before you can comment on or make changes to this bug.