[
https://issues.apache.org/jira/browse/MRESOLVER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780461#comment-17780461
]
Alexey Loubyansky commented on MRESOLVER-391:
---------------------------------------------
[~cstamas] using the resolver directly, when I resolve a compile or runtime
classpath, i would not include direct dependencies with scope test and that
would work as expected.
But when I want to resolve a test classpath, I will also include direct
dependencies with scope test and end up with the tree posted above. As we
talked previously, I don't think this should be considered an expected outcome.
I mean, knowing the impl details, it is but, imo, it's not the desired result
for the majority of users. As a user, I can clearly see my direct dependencies
in the POM (hopefully, unless there is a parent hierarchy that contributes to
that), what happens deeper though is not evident but I'd like to be sure my
runtime classpath doesn't change "randomly" when running tests.
> 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)
