Maven 2 & 3

Version ranges cannot be used for artifacts with 'import' scope

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.2.1
  • Fix Version/s: Issues to be reviewed for 3.x
  • Component/s: None
  • Labels:
    None
  • Environment:
    Maven 2.2.1
  • Complexity:
    Intermediate
  • Number of attachments :
    0

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>

Activity

Hide
Permalink
Rob ten Hove added a comment -

Also affects Maven 3.x unfortunately

Show
Rob ten Hove added a comment - Also affects Maven 3.x unfortunately

People

  • Assignee:
    Unassigned
    Reporter:
    Rob ten Hove
Vote (11)
Watch (12)

Dates

  • Created:
    Updated: