You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2011/12/27 13:59:04 UTC

[jira] (MDEP-245) goal to check classpath for duplicate resources/classes

     [ https://jira.codehaus.org/browse/MDEP-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MDEP-245.
-------------------------------

    Resolution: Won't Fix
      Assignee: Robert Scholte  (was: Brian Fox)

This is a typical example of an enforcer-rule, which has already been written.

[maven-enforcer-plugin|http://maven.apache.org/plugins/maven-enforcer-plugin/]
[banDuplicateClasses rule|http://mojo.codehaus.org/extra-enforcer-rules/banDuplicateClasses.html]

                
> goal to check classpath for duplicate resources/classes
> -------------------------------------------------------
>
>                 Key: MDEP-245
>                 URL: https://jira.codehaus.org/browse/MDEP-245
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: New Feature
>            Reporter: Joerg Schaible
>            Assignee: Robert Scholte
>            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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira