[
https://issues.apache.org/jira/browse/MSHARED-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold updated MSHARED-47:
-----------------------------------------
Fix Version/s: maven-dependency-analyzer-next-release
> maven-dependency-analyzer finds too many used dependencies
> ----------------------------------------------------------
>
> Key: MSHARED-47
> URL: https://issues.apache.org/jira/browse/MSHARED-47
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-analyzer
> Reporter: Matthew Beermann
> Priority: Major
> Labels: intern
> Fix For: maven-dependency-analyzer-next-release
>
> Attachments: MNG-3620-maven-dependency-analyzer.patch
>
>
> I'll just quote the post from our internal mailing list:
> "I don't like that plugin - it has reported dozens of missing dependencies
> that were unnecessary for me, so I stopped using it. The most common example
> is when you have a dependency on a project that has a dependency on Xerces,
> Xalan or some other XML project and your project has java.xml.* imports,
> which you're resolving from the JDK, it gives a higher priority to external
> dependencies, even if another project introduces them, than it does to JDK
> libraries."
> I've got a (possible) patch coming up in a few...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
