Description
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)
Attachments
Issue Links
- is depended upon by
-
MRESOLVER-277 --no-snapshot-update option does not prevent metadata.xml download
- Open
- relates to
-
MENFORCER-407 Enforcer 3.0.0 breaks with Maven 3.8.4
- Closed
-
MENFORCER-434 Version 3.1.0 is not enforcing bannedDependencies rules
- Closed
-
MENFORCER-437 DependencyConvergence treats provided dependencies are runtime dependencies
- Closed
-
MENFORCER-400 DependencyConvergence - poor error message
- Closed
-
MENFORCER-419 Upgrade Maven to 3.2.5
- Closed
- links to