[
https://issues.apache.org/jira/browse/MENFORCER-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703608#comment-17703608
]
Tamas Cservenak commented on MENFORCER-426:
-------------------------------------------
Slawek created reproducer for this use case and had following results (running
same IT w/ different enforcer version):
* 3.2.2-SNAPSHOT (current master) – FAILS
* 3.2.1 (uses resolver) -- FAILS
* 3.1.0 (uses old shared-dependency-tree) – FAILS
* 3.0.0 (uses old shared-dependency-tree) – FAILS
* 3.0.0-M3 (uses older shared-dependency-tree) – PASSES OK
Hence, it seems that it is this commit (that is present in 3.0.0 and upwards,
but not in 3.0.0-M3)
[https://github.com/apache/maven-enforcer/commit/ca40308fd58c45e638a35768b3966b5680d4c60e]
that causes this issue to become visible.
To make things more interesting, we do have a bug in "original" DF resolver
itself, recorded as MRESOLVER-345 that just complicates issue investigation
more (as this bug is present in all resolver versions, moreover in pre 3.9.0
Maven versions only DF was present).
For this we need some information from reporter [~jbarnett] :
* what Maven version you use?
* for statement "using version 3.0.0-M3 of the maven-enforcer-plugin's
DependencyConvergence rule passes. Using version 3.1.0 starts to show
convergence errors" you hopefully used same Maven version (that in bullet
above)?
> DependencyConvergence in 3.1.0 fails when using version ranges
> --------------------------------------------------------------
>
> Key: MENFORCER-426
> URL: https://issues.apache.org/jira/browse/MENFORCER-426
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: dependencyConvergence, Standard Rules
> Affects Versions: 3.0.0, 3.1.0
> Reporter: Joe Barnett
> Assignee: Slawomir Jaranowski
> Priority: Major
>
> In our project, using version 3.0.0-M3 of the maven-enforcer-plugin's
> DependencyConvergence rule passes. Using version 3.1.0 starts to show
> convergence errors that I believe may be related to using version ranges to
> declare dependencies:
> {code:java}
> [WARNING]
> Dependency convergence error for com.trib3:graphql:jar:1.32.3279:compile
> paths to dependency are:
> +-com.joe.quizzy:server:jar:1.0-SNAPSHOT
> +-com.joe.quizzy:graphql:jar:1.0-SNAPSHOT:compile
> +-com.trib3:graphql:jar:1.32.3279:compile
> and
> +-com.joe.quizzy:server:jar:1.0-SNAPSHOT
> +-com.trib3:graphql:jar:1.32.3324:compile
> {code}
> both {{com.joe.quizzy:server}} and {{com.joe.quizzy:graphql}} declare a
> dependency on {{com.trib3:graphql}}, with a version of
> {{[1.32.1,1.33-SNAPSHOT)}}. that version range should (currently) resolve to
> 1.32.3324 in both usages, but in enforcer 3.1.0's DependencyConvergence check
> does not.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
