[jboss-jira] [JBoss JIRA] (JASSIST-206) API breakage: javassist.util.proxy.RuntimeSupport.findMethod has changed signature
Marek Novotny (JIRA)
jira-events at lists.jboss.org
Thu Jul 11 16:24:21 EDT 2013
[ https://issues.jboss.org/browse/JASSIST-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789215#comment-12789215 ]
Marek Novotny commented on JASSIST-206:
---------------------------------------
yes, that is true. You can easily run Seam core unit test https://github.com/seam2/jboss-seam/blob/Seam_2_3/jboss-seam/src/test/java/org/jboss/seam/test/unit/CoreTest.java to simulate the NoSuchMethodError
> API breakage: javassist.util.proxy.RuntimeSupport.findMethod has changed signature
> ----------------------------------------------------------------------------------
>
> Key: JASSIST-206
> URL: https://issues.jboss.org/browse/JASSIST-206
> Project: Javassist
> Issue Type: Bug
> Affects Versions: 3.17.0-GA, 3.17.1-GA, 3.18.0-GA
> Environment: JBoss Seam 2.x
> Reporter: Andrei Ivanov
> Assignee: Shigeru Chiba
> Priority: Blocker
>
> Now that JASSIST-183 is fixed, I tried again just to discover that another public method has changed signature, breaking JBoss Seam:
> {noformat}
> java.lang.NoSuchMethodError: javassist.util.proxy.RuntimeSupport.findMethod(Ljava/lang/Object;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/reflect/Method;
> {noformat}
> Called by:
> http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/releases/org.jboss.seam/jboss-seam/2.2.0.GA/org/jboss/seam/util/ProxyFactory.java
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list