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

Compatibility with jnr-ffi 2.1.9 #72

Open
apetersson opened this issue Jan 1, 2019 · 2 comments
Open

Compatibility with jnr-ffi 2.1.9 #72

apetersson opened this issue Jan 1, 2019 · 2 comments

Comments

@apetersson
Copy link

apparently, there was a change inside NativeClosureManager (jnr-ffi) between version 2.1.9 and 2.1.7. by having web3j v 4.1.0 as a dependency, i accidentally bumped jnr-ffi to 2.1.9 which caused jnr-fuse to break (but only for readdir). Fixed this via a custom resolutionStrategy in my build.gradle. It would be nice to have compatibility with jnr-ffi 2.1.9

The cause is the call

        Field classLoaderField = NativeClosureManager.class.getDeclaredField("classLoader");

which happens in ClosureHelper, NativeClosureManager appears to have changed in its internal structure.

This is an issue because it is easy to accidentally bump jnr-ffi to 2.1.9 f.ex. when depending on other libs that declare it.

@apetersson
Copy link
Author

strongly related to #59 - a simple version bump is not sufficient.

@SerCeMan
Copy link
Owner

SerCeMan commented Jan 3, 2019

Hey, @apetersson!

Thank you for the report, it should be fixed by #61. The PR is currently blocked on jnr/jnr-ffi#169.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants