[
http://jira.codehaus.org/browse/MNG-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232311#action_232311
]
Jean-Noel Rouvignac commented on MNG-4550:
------------------------------------------
Clirr could help you check the binary compatibility:
* http://clirr.sourceforge.net/
* http://mojo.codehaus.org/clirr-maven-plugin/
> Binary incompatible changes in PluginManagerException and others
> ----------------------------------------------------------------
>
> Key: MNG-4550
> URL: http://jira.codehaus.org/browse/MNG-4550
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 2.2.1
> Reporter: Kohsuke Kawaguchi
> Fix For: 2.2.2
>
>
> As of 2.0.9, [PluginManagerException had a constructor that takes
> (String,Exception)|http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.9/maven-core/src/main/java/org/apache/maven/plugin/PluginManagerException.java]
> but in 2.2.1, [it now takes
> (String,Exception)|http://svn.apache.org/repos/asf/maven/maven-2/tags/maven-2.2.1/maven-core/src/main/java/org/apache/maven/plugin/PluginManagerException.java].
> This is a binary incompatible change that causes a LinkageError if code
> compiled against older version of the PluginManagerException is run with
> later version of Maven.
> The old constructor needs to be added back to remain binary compatible.
--
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
