Bug 990421 - [warning] Bad versioning during CR1 release
[warning] Bad versioning during CR1 release
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Portal Packaging (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 6.1.1
Assigned To: hfnukal@redhat.com
Dominik Pospisil
Depends On:
  Show dependency treegraph
Reported: 2013-07-31 03:36 EDT by Rob Stryker
Modified: 2013-12-03 08:16 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-12-03 08:16:46 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rob Stryker 2013-07-31 03:36:00 EDT
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:

Actual results:

Expected results:

Additional info:
Comment 2 hfnukal@redhat.com 2013-12-03 08:16:46 EST
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.