You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Matthew Beermann (JIRA)" <ji...@codehaus.org> on 2008/06/10 23:52:12 UTC
[jira] Created: (MNG-3620) maven-dependency-analyzer finds too many
used dependencies
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
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
[jira] Updated: (MSHARED-47) maven-dependency-analyzer finds too
many used dependencies
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHARED-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MSHARED-47:
-----------------------------------
Component/s: maven-dependency-analyzer
> 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
> Components: maven-dependency-analyzer
> 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
[jira] Commented: (MNG-3620) maven-dependency-analyzer finds too
many used dependencies
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138101#action_138101 ]
Brian Fox commented on MNG-3620:
--------------------------------
Cool. We should introduce a flag to the plugin to optionally ignore this, but looks good
> 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
[jira] Updated: (MNG-3620) maven-dependency-analyzer finds too many
used dependencies
Posted by "Matthew Beermann (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MSHARED-47) maven-dependency-analyzer finds too
many used dependencies
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MSHARED-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=279861#comment-279861 ]
Herve Boutemy commented on MSHARED-47:
--------------------------------------
I'm interested in this issue and have a few questions:
- can you give me an example of such an artifact having a dependency on Xerces? I need to write a unit test
- parsing the whole jdk does probably take a lot of time and memory: did you try to measure it?
another idea would be to use [JDK's api package list|http://svn.apache.org/viewvc/maven/plugins/trunk/maven-javadoc-plugin/src/main/resources/org/apache/maven/plugin/javadoc/] to detect classes to ignore: any objection?
> maven-dependency-analyzer finds too many used dependencies
> ----------------------------------------------------------
>
> Key: MSHARED-47
> URL: https://jira.codehaus.org/browse/MSHARED-47
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-analyzer
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MSHARED-47) maven-dependency-analyzer finds too many
used dependencies
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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