Bug 792990 (JBEPP-70) - Change Portal version from 4.3.0-SP1 to 4.3.0-CP1
Summary: Change Portal version from 4.3.0-SP1 to 4.3.0-CP1
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-70
Product: JBoss Enterprise Portal Platform 4
Classification: JBoss
Component: Portal
Version: 4.3.0.GA_CP1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3.0.GA_CP2
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-01 14:26 UTC by Joao Viragine
Modified: 2012-02-28 16:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
EPP 4.3 CP01
Last Closed: 2009-07-22 10:08:35 UTC
Type: Task

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-70 0 None None None Never

Description Joao Viragine 2009-05-01 14:26:16 UTC 
Date of First Response: 2009-05-04 03:09:59
project_key: JBEPP

PortalConstants uses: Version.Qualifier.Prefix.SNAPSHOT

AFAIK, SP1 should be CP1 or even better: CP01

This may confuse our customer.
Comment 1 Thomas Heute 2009-05-04 07:09:59 UTC 
It's using Version.Qualifier.Prefix.SP == Service Pach (which is equivalent to Cummulative patch).

The reason why it was not showing CP is that CP didn't exist and we would have had to reissue a new versoin of the common module very late in the process :-/

Agreed though that for next time we should change to CP, Jira will help to remember
Comment 2 Thomas Heute 2009-07-22 10:08:35 UTC 
Next release will show CP02
Note You need to log in before you can comment on or make changes to this bug.