-
-
Notifications
You must be signed in to change notification settings - Fork 96
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
Objenesis can't be compiled on Android SDK < 26 #79
Comments
…MethodHandle.invokeExact are only supported starting with Android O Cause: easymock/objenesis#79
…MethodHandle.invokeExact are only supported starting with Android O Cause: easymock/objenesis#79
@henri-tremblay The main issue for supporting android SDK < 26 is any mention of The Java 11 support added this and broke Android. -> 5f9d20b I think it will be hard to have a single jar that works on android API < 26 and JDK 11+. Providing multiple different artifacts is one possible solultion. Perhaps with a |
I'm a bit overwhelm these day. I do hope I will have the time to revisit soon. If anyone has the time, feel free to look. |
I have pushed the changes moving some instantiators in a new project. Could you please check if it works? I'm still not sure it's a good idea. JPMS requires me to change the package of the moved classes. I'm afraid of what I will break but I hope they are not that used. The alternative is indeed to play with classifiers. |
See mockito/mockito#2007.
The current possible solution can be to remove "exotic" instantiator from objenesis-core. We should have a test to make sure it works.
The text was updated successfully, but these errors were encountered: