[
http://jira.codehaus.org/browse/MNG-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew Beermann updated MNG-3620:
----------------------------------
Attachment: MNG-3620-maven-dependency-analyzer.patch
> maven-dependency-analyzer finds too many used dependencies
> ----------------------------------------------------------
>
> Key: MNG-3620
> URL: http://jira.codehaus.org/browse/MNG-3620
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: Shared Components
> Reporter: Matthew Beermann
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
