[
https://issues.apache.org/jira/browse/MRESOLVER-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17256356#comment-17256356
]
William Leung edited comment on MRESOLVER-98 at 12/30/20, 7:51 AM:
-------------------------------------------------------------------
[~michael-o]
Please check [https://github.com/apache/maven-resolver-ant-tasks/pull/2]
and the two added test cases from
[https://github.com/apache/maven-resolver-ant-tasks/pull/2/files#diff-0e9495413c05df4b700eff32a368c03643597dc72fd372c559d9e850f162f321]
- {{testResolvePomWithManagedDeps}} (resolved)
- {{testResolvePomWithScopedAndManagement}} (not yet)
was (Author: william-leung):
[~michael-o]
Please check https://github.com/apache/maven-resolver-ant-tasks/pull/2
and the two added test case from
https://github.com/apache/maven-resolver-ant-tasks/pull/2/files#diff-0e9495413c05df4b700eff32a368c03643597dc72fd372c559d9e850f162f321
- {{testResolvePomWithManagedDeps}} (resolved)
- {{testResolvePomWithScopedAndManagement}} (not yet)
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
