[jira] Commented: (MNG-4463) Version ranges cannot be used for artifacts with 'import' scope

["Rob ten Hove (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208332#action_208332 ] 

Rob ten Hove commented on MNG-4463:
-----------------------------------

Also affects Maven 3.x unfortunately :-(

> Version ranges cannot be used for artifacts with 'import' scope
> ---------------------------------------------------------------
>
>                 Key: MNG-4463
>                 URL: http://jira.codehaus.org/browse/MNG-4463
>             Project: Maven 2 & 3
>          Issue Type: Bug
>    Affects Versions: 2.2.1
>         Environment: Maven 2.2.1
>            Reporter: Rob ten Hove
>
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira