You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/06/13 04:23:12 UTC
[jira] Moved: (MSHARED-47) maven-dependency-analyzer finds too many
used dependencies
[ http://jira.codehaus.org/browse/MSHARED-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MNG-3620 to MSHARED-47:
------------------------------------------
Component/s: (was: Dependencies)
Key: MSHARED-47 (was: MNG-3620)
Project: Maven Shared Components (was: Maven 2)
> maven-dependency-analyzer finds too many used dependencies
> ----------------------------------------------------------
>
> Key: MSHARED-47
> URL: http://jira.codehaus.org/browse/MSHARED-47
> Project: Maven Shared Components
> Issue Type: Bug
> Reporter: Matthew Beermann
> Assignee: Brian Fox
> 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