[
https://issues.apache.org/jira/browse/MENFORCER-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460389#comment-17460389
]
Alexander Kriegisch commented on MENFORCER-277:
-----------------------------------------------
For documentation purposes: Upgrading Dependency Tree from 2.2. to 3.1.0 also
solved a 5 years old problem in Enforcer which I had accidentally reported in
the [Extra Enforcer Rules project as issue
#28|https://github.com/mojohaus/extra-enforcer-rules/issues/28]. Only after
yesterday the issue was closed by a maintainer and I looked into it again, I
found out that it was an issue in built-in rule {{dependencyConvergence}}, not
in any extra rule. Back then, probably I had too many project websites open and
reported in the wrong bug tracker.
Should I add the integration test I used during {{git bisect}} in order to find
the commit which fixed the problem to this project as a regression IT via PR?
> Upgrade maven-dependency-tree to 3.x
> ------------------------------------
>
> Key: MENFORCER-277
> URL: https://issues.apache.org/jira/browse/MENFORCER-277
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Affects Versions: 1.4.1
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Major
> Labels: S2
> Fix For: 3.0.0
>
> Attachments: MENFORCER-277.patch
>
>
> As part of MENFORCER-264 maven-dependency-tree should be upgraded. This would
> imply switching from the M2 {{DependencyTreeBuilder}} to M2/M3
> {{DependencyGraphBuilder}}.
> However, {{DependencyGraphBuilder}} uses {{ProjectDependenciesResolver}},
> which provides the *resolved* graph instead of a raw tree.
> This is a requirement for both {{DependencyConvergence}} and
> {{RequireUpperBoundDeps}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
