Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JavaSupport refactoring API (byte-code) incompatibility with extensions #2585

kares opened this Issue Feb 11, 2015 · 3 comments


None yet
3 participants
Copy link

kares commented Feb 11, 2015

on 9K (recently - not in preview1) JavaSupport was changed from class to interface, such change for extension APIs is hard to support without re-compiling ... esp. hard to target 1.7 and 9K at the same time.

sample failure seen on travis-ci :

 Java::JavaLang::IncompatibleClassChangeError: Found interface org.jruby.javasupport.JavaSupport, but class was expected

... coming from a simple: runtime.getJavaSupport().loadJavaClassVerbose(name);

such call is likely also in JRuby-OpenSSL that I know of (besides AR-JDBC), not sure for other extensions out there ... just wanted to let you guys know - as far as I see it's mostly due mocking/truffle


This comment has been minimized.

Copy link

chrisseaton commented Feb 26, 2015

Yes this is to support AOT compilation of JRuby. I can do it with an abstract class as well though.


This comment has been minimized.

Copy link
Member Author

kares commented Feb 26, 2015

@chrisseaton that would be a win-win ... thanks!


This comment has been minimized.

Copy link
Member Author

kares commented Mar 2, 2015

compatibility restored at bf8a55a ... thanks!

@kares kares closed this Mar 2, 2015

@enebo enebo added this to the milestone Apr 28, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.