You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2011/02/24 14:08:23 UTC

[jira] Closed: (MNG-5006) [regression] Resolution of parent POMs for dependency using version range does not consider all configured repositories

     [ http://jira.codehaus.org/browse/MNG-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann closed MNG-5006.
----------------------------------

    Resolution: Fixed
      Assignee: Benjamin Bentmann

Fixed in [r1074131|http://svn.apache.org/viewvc?view=revision&revision=1074131], thanks for the example project.

> [regression] Resolution of parent POMs for dependency using version range does not consider all configured repositories
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-5006
>                 URL: http://jira.codehaus.org/browse/MNG-5006
>             Project: Maven 2 & 3
>          Issue Type: Bug
>    Affects Versions: 3.0.2
>         Environment: WinXP SP3, Java 6u20
>            Reporter: Kristoffer Peterhansel
>            Assignee: Benjamin Bentmann
>             Fix For: 3.0.3
>
>         Attachments: maven-version-range-test.zip, maven-version-range-test2.zip, mvn-verify-fixed-version.log, mvn-verify-offline.log, mvn-verify-range-version.log
>
>
> I have a bit of a strange issue. When running under Maven 3.0.2 I am getting build errors when I try to build one of our projects when one of their dependencies have a range version. But when setting it to a specific version it seems to work. The same project works without a hitch in Maven 2.2.1.
> As can be seen from the first included verbose trace (mvn-verify-range-version.log). Maven attempts to get the pom from our snapshot repository. That will, obviously, not work for a released artefact.
> Changing the dependency version from the [1,2) range to 1.0.1-SNAPSHOT seems to skip that step completely. Even though it resolves to the same version in the end. As seen in the other verbose trace (mvn-verify-fixed-version.log)

-- 
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