Bug 793063 (JBEPP-145) - EPP CPs are only distributed as a complete product distribution, not as "patches"
Summary: EPP CPs are only distributed as a complete product distribution, not as "patc...
Keywords:
Status: CLOSED NOTABUG
Alias: JBEPP-145
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: unspecified
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.x
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-22 20:27 UTC by Aaron Pestel
Modified: 2012-02-28 16:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
EPP 4.3
Last Closed: 2012-01-05 10:52:10 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-145 0 None None None Never

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
Note You need to log in before you can comment on or make changes to this bug.