Using a version range in a plugin dependency causes "failure to resolve
artifact" error
---------------------------------------------------------------------------------------
Key: MNG-2742
URL: http://jira.codehaus.org/browse/MNG-2742
Project: Maven 2
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.0.4
Environment: Windows XP SP2, java version "1.5.0_08"
Reporter: Matthew Adams
Attachments: pom.xml
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira