Bug 900081 (JBPAPP6-1575)

Summary:	Update vman to generate valid OSGi versions
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Paul Gier <pgier>
Component:	Build	Assignee:	John Casey <jdcasey>
Status:	CLOSED EOL	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	jdcasey, ncross, pgier
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBPAPP6-1575
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-19 12:48:59 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	928004

Description Paul Gier 2012-03-22 16:30:13 UTC

project_key: JBPAPP6

Currently the vman tool produces some invalid OSGi versions.  We should research different options for making things more compatible with OSGi.  Here are a couple basic examples of the current behaviour:
1.0.0.Final -> 1.0.0.Final-redhat-1 (valid OSGi version)
1.0.0 -> 1.0.0-redhat-1 (Invalid OSGi, should be 1.0.0.redhat-1)

Some more info in the wiki (https://docspace.corp.redhat.com/docs/DOC-39079)

Comment 1 Paul Gier 2012-03-22 16:31:11 UTC

Link: Added: This issue is related to JBPAPP-7929

Comment 2 Paul Gier 2012-03-22 16:31:12 UTC

JBPAPP-7929 is the QA test results which show which versions are currently not following the OSGi standard.

Comment 3 John Casey 2012-08-09 21:54:29 UTC

To be safe and consistent, can we just change the version suffix to .redhat-1 across the board, instead of -redhat-1?

Comment 4 Paul Gier 2012-08-10 21:13:41 UTC

Unfortunately that would also create invalid versions because OSGi does not allow "." in the qualifier.
1.0.0.Final -> 1.0.0.Final.redhat-1 (invalid OSGi version)

Comment 5 Anne-Louise Tangring 2012-11-13 21:13:20 UTC

Docs QE Status: Removed: NEW

Comment 6 Paul Gier 2013-04-09 19:48:55 UTC

EAP QA job which checks for valid artifact versions in the EAP Maven repository
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Repository/job/eap-60-repository-maven-check-valid-versions/

Comment 7 Paul Gier 2013-04-09 19:55:00 UTC

Information about valid OSGi versions here:
https://community.jboss.org/wiki/JBossProjectVersioning

For the scope of this issue, I think it's enough to just add the ability to handle the common case where the upstream version has three components with no qualifier.  For example,
1.0.0 -> 1.0.0.redhat-1

For correct handling of versions which don't include a micro version (for example 1.0.GA), that can be discussed in a separate issue once the first part is working.

Some specific examples of invalid OSGi versions can be seen in the EAP QA job which checks artifact versions in the EAP Maven repository
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Repository/job/eap-60-repository-maven-check-valid-versions/