Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 348767 - Version ranges of dependencies contain qualifier
Summary: Version ranges of dependencies contain qualifier
Status: RESOLVED FIXED
Alias: None
Product: Dash
Classification: Technology
Component: Maven (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Dash Incoming bugs CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-08 11:34 EDT by Aaron Digulla CLA
Modified: 2011-07-06 11:56 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Digulla CLA 2011-06-08 11:34:58 EDT 
Jason van Zyl reports:

The problem I have found is that you generate specific projects with their POM with concrete versions, say 2.5.0.

But then in the dependency element of a project that requires that dependency you use a range like:

[2.5.0.v200906151043,3.0.0)

And this will not work because 2.5.0.v200906151043 is higher then 2.5.0 so Maven isn't going to find 2.5.0 as satisfactory.

Why don't you just generate with the concrete version 2.5.0 in the dependency requirement.

The specific case I cite here is:

No versions available for org.eclipse.emf:org.eclipse.emf.ecore.xmi:jar:[2.5.0.v200906151043,3.0.0)

Your script generated 2.5.0 of org.eclipse.emf.ecore.xmi, but dependencies on org.eclipse.emf.ecore.xmi are encoded with a range that is invalid.
Comment 1 Aaron Digulla CLA 2011-06-08 11:37:15 EDT 
I'll extend the patch tool m4e-apply-patches.py to strip the qualifier from the version ranges.
Comment 2 Aaron Digulla CLA 2011-07-06 11:56:00 EDT 
This has been fixed.