[
https://issues.apache.org/jira/browse/MRESOLVER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780307#comment-17780307
]
Alexey Loubyansky commented on MRESOLVER-391:
---------------------------------------------
> As such the example is consistent in test and runtime.
Not really. The runtime classpath will contain a different version of
acme-lib-c (and possibly its dependencies). Imagine there are consumers of
acme-product-a, that add acme-product-a as a dependency.
Unless acme-product-a includes integration tests, acme-product-a will be tested
having acme-lib-c:2.0.0-SNAPSHOT on its test classpath and then packaged up and
deployed to Maven. Projects depending on acme-product-a will see that it
depends (transitively) on acme-lib-c:1.0.0-SNAPSHOT, although acme-product-a
was tested having a different version acme-lib-c on its classpath.
> 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)
