Bug 793063 (JBEPP-145)

Summary: EPP CPs are only distributed as a complete product distribution, not as "patches"
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: Aaron Pestel <ammppp>
Component: unspecifiedAssignee: Default User <jbpapp-maint>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: epp-bugs, joao.viragine, luc.texier
Target Milestone: ---   
Target Release: 5.2.x   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-145
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
EPP 4.3
Last Closed: 2012-01-05 10:52:10 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:27:54 UTC 
Date of First Response: 2009-10-22 16:33:42
project_key: JBEPP

EPP 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 3 Jared MORGAN 2011-11-17 23:16:15 UTC 
Release Notes Docs Status: Added: Not Required