[MDEP-779] dependency:analyze should list the classes that cause a used undeclared dependency

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.3.0
• Component/s: analyze-dep-mgt
• Assignee: Slawomir Jaranowski
• Reporter: Joseph Walton
• Created: 05/Dec/21 03:11
• Updated: 01/Feb/22 22:01
• Resolved: 01/Feb/22 22:01

Description

When dependency:analyze shows that a module has used classes from an undeclared dependency, it may not be clear which classes are involved. In particular, on large projects where modules and packages don't have a clear 1:1 relationship.

It would be useful if there was (opt-in?) display of the classes involved. This could make it significantly quicker to identify the specific issue without switching to another tool.

For example:

[WARNING] Used undeclared dependencies found:
[WARNING]    xml-apis:xml-apis:jar:1.0.b2:compile
[WARNING]        class org.apache.xmlcommons.Version

Issue Links

• is blocked by: MSHARED-1020 Include class names in used undeclared dependencies
• relates to: MSHARED-632 Expose which dependency classes are used and where
• links to: GitHub Pull Request #178