[
https://issues.apache.org/jira/browse/MRESOLVER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770028#comment-17770028
]
Alexey Loubyansky edited comment on MRESOLVER-391 at 9/28/23 12:11 PM:
-----------------------------------------------------------------------
I think this should also cover provided scope. Meaning compile and runtime
should be preferred over test and provided.
In addition to that, it should also *not* be limited to the distance to the
root node. If conflicting versions appear to be on the same depth level but the
test or provided scoped dependency branch appears before the compile or runtime
one, the compile/runtime node should win.
was (Author: aloubyansky):
I think this should also cover provided scope. In addition to that, it should
also not be limited to the distance to the root node but also on the ordering
of the dependencies. E.g. if conflicting versions appear to be on the same
depth level but the test or provided scoped dependency branch appears before
the compile or runtime one.
> Scope mediation improvements
> ----------------------------
>
> Key: MRESOLVER-391
> URL: https://issues.apache.org/jira/browse/MRESOLVER-391
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0
>
>
> As per MNG-5988: if an artifact in "test" scope is found nearer, but in scope
> "compile" is found deeper in graph, the "test" scope wins. This at runtime
> may lead to CNFEx.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
