[jira] Updated: (MNG-3491) JAR hell detection

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-3491:
------------------------------

    Fix Version/s: 2.x

seems best served by the enforcer plugin or similar, but worth considering in some core way in the future

> JAR hell detection
> ------------------
>
>                 Key: MNG-3491
>                 URL: http://jira.codehaus.org/browse/MNG-3491
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Dependencies
>    Affects Versions: 2.0.8
>            Reporter: Andreas Krüger
>             Fix For: 2.x
>
>
> When your dependency tree contains the same class twice in two different versions, you are in JAR hell.
> I want Maven to detect whether that's where I am. So Maven should:
> * Open all JARs it has added to a dependency tree.
> * Check what classes are in each JAR (package name and class name).
> * If the same class is found twice in two different JARs, I want Maven to
> ** compare the two instances
> ** fail the build unless they turn out to be bytewise identical.
> All of these things should happen automatically, with every individual dependency tree.
> Unless the user specifically requests. E.g., if the user knows a particular set of classes is officially in the dependency tree (e.g., of a test), but never actually loaded, it should be possible to accept different versions of these classes (some wild card pattern).
> Regards, and thank you for providing fine software,
> Andreas

-- 
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