Rob ten Hove opened MNG-4463 and commented

Version ranges cannot be used for artifacts with import scope. If a version range is used for such an artifact, Maven cannot find it. Looking at the console output shows that it takes the version range as the version, without resolving it:

Downloading: http://some-repo/group/artifact/[1.0.0,2.0.0)/artifact-[1.0.0,2.0.0).pom

This is the POM snippet:

<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>group</groupId>
      <artifactId>artifact</artifactId>
      <version>[1.0.0,2.0.0)</version>
      <!-- Using e.g. <version>1.1.0</version> does work! -->
      <type>pom</type>
      <scope>import</scope>
    </dependency>
  </dependencies>
</dependencyManagement>

Affects: 2.2.1

Issue Links:

• MNG-6656 Introduce base for build/consumer process
  ("is part of")

Remote Links:

• Page
  
• GitHub Pull Request #28
  
• GitHub Pull Request #146
  
• GitHub Pull Request #28
  
• GitHub Pull Request #146
  

Backported to: 4.0.0-alpha-2

17 votes, 32 watchers