Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-5006

[regression] Resolution of parent POMs for dependency using version range does not consider all configured repositories

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.2
    • Fix Version/s: 3.0.3
    • Component/s: None
    • Labels:
      None
    • Environment:
      WinXP SP3, Java 6u20

      Description

      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)

        Attachments

          Activity

            People

            • Assignee:
              bentmann Benjamin Bentmann
              Reporter:
              kristoffer Kristoffer Peterhänsel
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: