[MECLIPSE-531] eclipse:to-maven uses version ranges in pom.xmls created, which fail version checking

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Auto Closed
• Affects Version/s: 2.5.1
• Environment: Windows XP SP3, Maven 2.0.9, Java 1.6.0.11
• Assignee: Unassigned
• Reporter: Costin Caraivan
• Created: 05/Mar/09 08:37
• Updated: 06/Sep/15 20:43
• Resolved: 06/Sep/15 20:43

Description

If you use eclipse:to-maven, the resulting artifacts have poms containing versions like these, for dependencies: [3.2.0,4.0.0).

End result =>

Couldn't find a version in [3.2.0-v3232o] to match range [3.2.0,4.0.0)

I believe that to-maven needs an option like make-artifacts, to resolveVersionRanges, because stripping qualifiers means that we lose information (Eclipse 3.4 has some 3.2.0 plugins for example, but with a different qualifier than the original 3.2 Eclipse plugins).

Or the version ranges need to be fixed, something like this: [3.2.0-, 4.0.0-).

Thank you.