Bug 990421

Summary:	[warning] Bad versioning during CR1 release
Product:	[JBoss] JBoss Enterprise Portal Platform 6	Reporter:	Rob Stryker <rstryker>
Component:	Portal Packaging	Assignee:	hfnukal <hfnukal>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Dominik Pospisil <dpospisi>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	epp-bugs, jpallich, theute
Target Milestone:	---
Target Release:	6.1.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-03 13:16:46 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:
Embargoed:

Description Rob Stryker 2013-07-31 07:36:00 UTC

Description of problem:
I realize this is not terribly timely or recent. On my disk i have the following build: jboss-jpp-6.0.0.CR01.1.zip

JBossTools routinely reads some data such as version information from the manifest files inside the server. For this specific build, jboss-jpp-6.0/modules/org/jboss/as/product/jpp/dir/META-INF/MANIFEST.MF  had the following line:

JBoss-Product-Release-Version: 6.0.0.CR01.1

We use osgi Version class to read this version string and compare it to other version strings. Unfortunately, this class does not recognize "6.0.0.CR01.1" as a valid version string. 

It'd be nice if respins (which I assume this was?) in the future use valid osgi version strings, such as "6.0.0.CR01a". 

This is mostly a warning, but it would be critical if a major release suffered from this error. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 hfnukal@redhat.com 2013-12-03 13:16:46 UTC

I will keep this in mind for fix releases.