You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/01/28 01:46:55 UTC
[jira] Updated: (MNG-4550) Binary incompatible change in
PluginManagerException
[ http://jira.codehaus.org/browse/MNG-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-4550:
------------------------------
Fix Version/s: 2.2.2
> Binary incompatible change in PluginManagerException
> ----------------------------------------------------
>
> 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