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)
Link: Added: This issue is related to JBPAPP-7929
JBPAPP-7929 is the QA test results which show which versions are currently not following the OSGi standard.
To be safe and consistent, can we just change the version suffix to .redhat-1 across the board, instead of -redhat-1?
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)
Docs QE Status: Removed: NEW
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/
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/