You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joseph Walton (Jira)" <ji...@apache.org> on 2021/12/05 06:41:00 UTC
[jira] [Updated] (MDEP-779) dependency:analyze should list the classes that cause a used undeclared dependency
[ https://issues.apache.org/jira/browse/MDEP-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Walton updated MDEP-779:
-------------------------------
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:
{noformat}
[WARNING] Used undeclared dependencies found:
[WARNING] xml-apis:xml-apis:jar:1.0.b2:compile
[WARNING] class org.apache.xmlcommons.Version
{noformat}
was:
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}
> 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
>
> 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)