Bug 990421 - [warning] Bad versioning during CR1 release
Summary: [warning] Bad versioning during CR1 release
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Portal Packaging
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 6.1.1
Assignee: hfnukal@redhat.com
QA Contact: Dominik Pospisil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-31 07:36 UTC by Rob Stryker
Modified: 2013-12-03 13:16 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-12-03 13:16:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.