[MNG-2742] Using a version range in a plugin dependency causes "failure to resolve artifact" error

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Incomplete
• Affects Version/s: 2.0.4
• Component/s: Dependencies
• Environment: Windows XP SP2, java version "1.5.0_08"
• Assignee: Unassigned
• Reporter: Matthew T. Adams
• Created: 05/Jan/07 14:11
• Updated: 02/Jul/14 08:44
• Resolved: 22/Jan/14 20:31

Description

If I declare a dependency in a plugin using an exact version, Maven correctly resolves the artifact. If, however, I change the dependency's version to a version range, Maven no longer resolves the artifact. I'm using the very same artifact and version range in my project's dependencies and everything works ok. See my attached pom.xml file for details, in particular, the comments "<!-- Using version range here ok ->" and "<!- Can't use version range here! -->".

I am using the "major.minor.revision-buildNumber" version string syntax as described on the wiki.

Issue Links

• is related to: MNG-2906 version ranges don't work after a day has passed
• is related to: MNG-3010 Problem parsing version ranges