[
http://jira.codehaus.org/browse/MDEP-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214007#action_214007
]
luke w patterson commented on MDEP-245:
---------------------------------------
One option for now is JBoss' Tattletale tool: http://www.jboss.org/tattletale
an example of its use:
http://insuchaworld.blogspot.com/2010/03/using-jboss-tattletale-tool-in-maven.html
> goal to check classpath for duplicate resources/classes
> -------------------------------------------------------
>
> Key: MDEP-245
> URL: http://jira.codehaus.org/browse/MDEP-245
> Project: Maven 2.x Dependency Plugin
> Issue Type: New Feature
> Reporter: Joerg Schaible
> Assignee: Brian Fox
> Priority: Minor
>
> The classpath sometimes contains unintended duplicate resources and classes
> e.g.:
> # an artifact is present in two different versions at the same time, because
> it changed its groupId or artifactId, but no relocation POM has been provided
> by the artifact's author
> # an artifact has been split into several artifacts (avalon-famework =>
> avalon-framework-api and avalon-framework-impl)
> # an artifact has a collection of "foreign" classes (CGLIB 2.x contains stuff
> from ASM 1.5)
> A new goal of the dependency plugin might detect such cases. Obviously there
> are cases, when this is expected (stax-api implements stuff provided also by
> JDK 6) or cannot be avoided in general (even xpp3_min contains two classes
> from xmlpull-api) or is even part of the spec (SPI files in
> META-INF/services).
--
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
