[
https://issues.apache.org/jira/browse/MDEP-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MDEP-779:
--------------------------------------
Fix Version/s: 3.3.0
> dependency:analyze should list the classes that cause a used undeclared
> dependency
> ----------------------------------------------------------------------------------
>
> Key: MDEP-779
> URL: https://issues.apache.org/jira/browse/MDEP-779
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: analyze-dep-mgt
> Reporter: Joseph Walton
> Priority: Major
> Fix For: 3.3.0
>
>
> 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:
> {noformat}
> [WARNING] Used undeclared dependencies found:
> [WARNING] xml-apis:xml-apis:jar:1.0.b2:compile
> [WARNING] class org.apache.xmlcommons.Version
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
