You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2022/10/04 14:17:00 UTC
[jira] [Updated] (MENFORCER-435) Get rid of maven-dependency-tree dependency
[ https://issues.apache.org/jira/browse/MENFORCER-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated MENFORCER-435:
--------------------------------------
Description: 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) (was: 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))
> 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
> Priority: Major
>
> 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)