maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-4463) Dependency management import should support version ranges.
Date Mon, 11 Dec 2017 16:35:18 GMT

    [ https://issues.apache.org/jira/browse/MNG-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286164#comment-16286164
] 

Hudson commented on MNG-4463:
-----------------------------

Build unstable in Jenkins: Maven TLP (wip) » maven » pre-reset-master #3

See https://builds.apache.org/job/maven-wip/job/maven/job/pre-reset-master/3/

> 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
>             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
(v6.4.14#64029)

Mime
View raw message