Bug 779146 (SOA-1544)

Summary: SOA-P CP patches are only distributed as full installations, not as "patches"
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Aaron Pestel <ammppp>
Component: Build ProcessAssignee: Default User <jbpapp-maint>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: atangrin, joao.viragine
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1544
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 779147 779148 (view as bug list) Environment:
SOA-P 4.3
Last Closed: 2009-12-02 11:52:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Aaron Pestel 2009-10-22 20:26:06 UTC 
Date of First Response: 2009-11-27 08:04:15
project_key: SOA

SOA-P 4.3 CPs are only distributed as complete product distributions as opposed to actual "patches".  There has two negative consequences for customers:

1.)  The CPs can not be applied via JON.
2.)  Installing a CP overwrites all changes (config, datasources, queue/topic settings, etc.) of a customer installation.  In some customer situations, this means they have to run through almost 100 pages of post installation procedures again after just installing a CP.  The CPs should not overwrite everything, should just include the actual changes that have been "fixed" in the CP.  Please note that EAP releases CPs both ways:  as a full distribution and as a patch distribution.
Comment 1 Mark Little 2009-11-27 13:04:15 UTC 
Remember to set Components in future.
Comment 2 trev 2009-12-02 11:52:12 UTC 
patch build system is tied into BREW, when we move build system this will be handled by BREW/MEAD