You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2020/01/25 10:12:00 UTC

[jira] [Updated] (MRESOLVER-98) resolver ant task doesn't appear to obey dependencyManagement

     [ https://issues.apache.org/jira/browse/MRESOLVER-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated MRESOLVER-98:
------------------------------------
    Fix Version/s: waiting-for-feedback

> resolver ant task doesn't appear to obey dependencyManagement
> -------------------------------------------------------------
>
>                 Key: MRESOLVER-98
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-98
>             Project: Maven Resolver
>          Issue Type: Bug
>          Components: ant tasks
>    Affects Versions: ant-tasks-1.2.0
>            Reporter: Jay Kahrman
>            Priority: Major
>             Fix For: waiting-for-feedback
>
>
> We have a dependency in our pom which has dependencies that don't specify an upper bound to the version range. To avoid getting different versions in every build we use a dependencyManagement section in the POM to lock down the version. This works via the maven 3 CLI, and via the old ant-tasks utility we were using (). The maven-resolver-ant-tasks jar doesn't appear to obey the dependencyManagement section, however. 
>  
> I'm not sure is this is related to MRESOLVER-33 and/or MRESOLVER-10 and if updating maven-resolver-ant-tasks to depend on Maven Resolver 1.4.0 would solve the problem.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)