Bug 536120 (RHQ-504) - Unify deployment workflow for deploy/re-deploy
Summary: Unify deployment workflow for deploy/re-deploy
Keywords:
Status: CLOSED WONTFIX
Alias: RHQ-504
Product: RHQ Project
Classification: Other
Component: Inventory
Version: 1.0
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact:
URL: http://jira.rhq-project.org/browse/RH...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-19 18:30 UTC by Jason Dobies
Modified: 2014-05-12 20:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-12 20:08:37 UTC
Embargoed:

Attachments (Terms of Use)

Description Jason Dobies 2008-05-19 18:30:00 UTC 
RHQ 1.0 has a working implementation of this, however I'm not sure it's ideal. There are some areas I'd like to refine:
- Updating the package for a package-backed resource
- Relationship between resource creation and package deployment (with respect to auditing as came up in RHQ-490)
Comment 1 Joseph Marques 2008-07-20 02:39:05 UTC 
jay, when would you like to review this?
Comment 2 Jason Dobies 2008-07-21 13:35:10 UTC 
Future.
Comment 3 Red Hat Bugzilla 2009-11-10 21:10:41 UTC 
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-504
This bug incorporates RHQ-490
Comment 4 Heiko W. Rupp 2010-08-10 15:52:03 UTC 
Actually we can currently deploy ear/war resources on AS level and re-deploy newer versions of the ear/war there too. 
This is not possible for other types of resources, that need to go through the content subsystem.
Note You need to log in before you can comment on or make changes to this bug.