[
https://issues.apache.org/jira/browse/MENFORCER-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645811#comment-17645811
]
Konrad Windszus commented on MENFORCER-435:
-------------------------------------------
I have a WIP version which I now pushed to
https://github.com/apache/maven-enforcer/tree/feature/remove-m-dependency-tree/enforcer-rules.
I am currently not working on this, so feel free to continue the branch. It is
not that easy as we need to stay backwards compatible, so probably it is not
really about getting rid of it in the first place, but only using the new
Resolver API in the first place. Only with a major version bump, we can finally
get rid of the m-dependency-tree dependency and all related code.
> Get rid of maven-dependency-tree dependency
> -------------------------------------------
>
> Key: MENFORCER-435
> URL: https://issues.apache.org/jira/browse/MENFORCER-435
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Assignee: Slawomir Jaranowski
> Priority: Major
>
> As the m-enforcer-p depends on Maven 3.2.5 (since MENFORCER-419) all
> dependency resolutions should be done with Aether API directly instead of
> leveraging https://maven.apache.org/shared/maven-dependency-tree/. At the
> same time the error message should print the full path to the affected
> dependency instead of forcing users to use a dedicated call of {{mvn
> dependency:tree}} to locate the dependency
> (https://github.com/apache/maven-enforcer/blob/a06b47ba079b342d69a49d3cbad0fb546000f734/enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/AbstractBanDependencies.java#L111)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
