[
https://issues.apache.org/jira/browse/MRESOLVER-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034012#comment-17034012
]
Kapil Somani commented on MRESOLVER-98:
---------------------------------------
Hi Michael,
I have carried out below experiment with both _fixed-stuff_ and
_1.2.0-source-release_ but the maven resolver doesn't seem to honor
dependencyManagement section of pom.xml
# Updated resolverVersion property in pom.xml to 1.4.0
# Updated mavenVersion property in pom.xml to 3.6.3 (since resolver-provider
3.5.0 had references to deprecated CacheUtils in resolver-imp-1.3.3.jar)
> 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)
