[
https://issues.apache.org/jira/browse/MRESOLVER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780493#comment-17780493
]
Tamas Cservenak commented on MRESOLVER-391:
-------------------------------------------
Problem with plugin m-dep-p is that is uses (ancient) "compatibility layers"
that are a ratnest.
So what is exactly you'd want to see as output? As IMHO this
{noformat}
prompt> graph org.acme:acme-product-a:jar:1.0.0-SNAPSHOT --excludeScopes=
[INFO] Collecting org.acme:acme-product-a:jar:1.0.0-SNAPSHOT
[INFO]
[INFO] org.acme:acme-product-a:jar:1.0.0-SNAPSHOT
[INFO] +- org.acme:acme-lib-d:jar:1.0.0-SNAPSHOT [test]
[INFO] | \- org.acme:acme-lib-c:jar:2.0.0-SNAPSHOT [compile]
[INFO] \- org.acme:acme-lib-b:jar:1.0.0-SNAPSHOT [compile]
[INFO] \- org.acme:acme-lib-c:jar:1.0.0-SNAPSHOT [compile] (conflicts with
2.0.0-SNAPSHOT)
{noformat}
Describes precisely what you have. Now, HOW is the "winner" (lib-c 2.0.0)
selected, is another story, but in general, this may be the case when Resolver
could give up? But then we soar into area where we should "judge" is some
conflict "compatible" or "incompatible", "semver" whatever...
> 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)
