[MENFORCER-400] DependencyConvergence - poor error message

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 3.0.0
• Component/s: Plugin, Standard Rules
• Assignee: Unassigned
• Reporter: T. Mohme
• Created: 05/Oct/21 07:58
• Updated: 19/Mar/23 09:37
• Resolved: 19/Mar/23 09:37

Description

For some dependencies that are not available I get only a very unspecific message like 

[WARNING] Rule 1: org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:
Could not build dependency tree Could not collect dependencies: com.acme:my-project:jar:1.0.0 ()

Only when running maven with "-X" I get a clue what is going on, but then I have to scan over 1600 lines of output to find what actually happened:

Caused by: org.eclipse.aether.collection.DependencyCollectionException: Failed to collect dependencies at com.acme:my-project:jar:1.0.0 -> io.quarkus:quarkus-flyway:jar:2.2.3.Final -> io.quarkus:quarkus-agroal:jar:2.2.3.Final -> io.quarkus:quarkus-narayana-jta:jar:2.2.3.Final -> org.jboss.narayana.jts:narayana-jts-integration:jar:5.12.0.Final -> org.jboss.narayana.jts:idlj-idl:jar:5.12.0.Final
...
Caused by: org.apache.maven.wagon.TransferFailedException: transfer failed for https://repository.jboss.org/nexus/content/repositories/thirdparty-releases/org/jboss/narayana/jts/idlj-idl/5.12.0.Final/idlj-idl-5.12.0.Final.pom

This information should somehow get collected internally when the problem happens and presented to the user together with the above mentioned warning log message.

Issue Links

• duplicates: MENFORCER-415 Violation messages can be really hard to find in a multi module project
• is related to: MENFORCER-435 Get rid of maven-dependency-tree dependency