[
https://issues.apache.org/jira/browse/MNG-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347255#comment-16347255
]
Robert Thornton commented on MNG-4463:
--------------------------------------
Does this fix also allow expressions in the version? For example:
<dependencyManagement><dependencies><dependency><groupId>group</groupId><artifactId>artifact</artifactId><version>${artifact.version}</version><type>pom</type><scope>import</scope></dependency></dependencies></dependencyManagement>
> Dependency management import should support version ranges.
> -----------------------------------------------------------
>
> Key: MNG-4463
> URL: https://issues.apache.org/jira/browse/MNG-4463
> Project: Maven
> Issue Type: Bug
> Affects Versions: 2.2.1
> Environment: Maven 2.2.1
> Reporter: Rob ten Hove
> Priority: Major
> Fix For: 3.5.x-candidate
>
>
> 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:
> {noformat}Downloading:
> http://some-repo/group/artifact/[1.0.0,2.0.0)/artifact-[1.0.0,2.0.0).pom{noformat}
> This is the POM snippet:
> {code:xml}
> <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>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
