Bug 900276 (JBPAPP6-625)

Summary: org.jboss.component.management:jboss-component-version-master contains wrong ranges
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Marius Bogoevici <mariusb>
Component: Maven RepositoryAssignee: Heiko Braun <ike.braun>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 6.0.0CC: rruss
Target Milestone: ---   
Target Release: EAP 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBPAPP6-625
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-09 02:55:15 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 Marius Bogoevici 2012-04-20 20:18:30 UTC
project_key: JBPAPP6

The ranges described in the pom contain ranges like:

{code}
 <version.xyz>[xyz,xyz-redhat-1]</version.xyz>
{code}

This scheme isn't actually correct, as 'redhat-1' is not a known qualifier (like 'ga', 'final', etc for which maven 3 actually supports xyz < xyz-ga). While this eventually works in Maven and Eclipse, may have side effects. and it definitely throws stricter tools like IntelliJ off (prevents importing Maven projects).

Comment 1 Paul Gier 2012-04-23 13:55:46 UTC
The version comparison changed in Maven 3 so that unknown qualifiers are assumed to be later than GA.  
So for Maven 3:
x.y.z < x.y.z-redhat-1
Compared to Maven 2.x:
x.y.z > x.y.z-redhat-1

Before the GA release we plan to remove all the ranges from the BOM and only use specific versions, so issues like what you are facing will go away.


Comment 2 Paul Gier 2012-04-23 13:59:02 UTC
Link: Added: This issue relates to JBPAPP-8805


Comment 3 Paul Gier 2012-05-04 02:38:55 UTC
Will be fixed in JBPAPP-8805

Comment 4 Anne-Louise Tangring 2012-11-05 17:45:09 UTC
Docs QE Status: Removed: NEW