Konrad Windszus created MENFORCER-435:
-----------------------------------------
Summary: 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
As the m-enforcer-p depens on Maven 3.2.5 (since MENFORCER-325) 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 be 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)