[MNG-4463] Dependency management import should support version ranges

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.1
• Fix Version/s: 4.0.0-alpha-2, 4.0.0
• Component/s: Dependencies
• Environment: Maven 2.2.1
• Assignee: Robert Scholte
• Reporter: Rob ten Hove
• Created: 23/Nov/09 09:39
• Updated: 20/Oct/22 08:11
• Resolved: 24/Sep/21 19:35

Description

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>

Issue Links

• is part of: MNG-6656 Introduce base for build/consumer process
• links to: GitHub Pull Request #28
• links to: GitHub Pull Request #28
• links to: GitHub Pull Request #146
• links to: GitHub Pull Request #146
• mentioned in: Page Loading...