You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mirko Raner (JIRA)" <ji...@codehaus.org> on 2009/05/16 03:58:45 UTC

[jira] Commented: (MNG-2742) Using a version range in a plugin dependency causes "failure to resolve artifact" error

    [ http://jira.codehaus.org/browse/MNG-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176707#action_176707 ] 

Mirko Raner commented on MNG-2742:
----------------------------------

We are currently struggling with similar issues, which, in our case, seem to be related to MNG-3518. The problem occurs only when version ranges are used and the plugin versions use the "major.minor.revision-buildNumber" format (i.e., an additional build qualifier that is separated by a dash and possibly starts with a non-numeric character). I was just wondering whether the issues are related; maybe MNG-2742 is even a duplicate of MNG-3518?
Anyway, I just wanted to make a note of a possible relation/duplication here...


> 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
>             Fix For: 3.x
>
>         Attachments: mvn.txt, 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