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
Java 9 and shading cglib #968
Comments
@sormuras thanks for reporting this, @PascalSchumacher has spiked using Java 9 in AssertJ, he might have more feedback than me on the subject. |
BTW, we are planning to release the next version of AssertJ 3.7.0 at the end of the month. |
Used jitpack.io to build your core "master-SNAPSHOT" artifact. Let's see what happens: https://travis-ci.org/junit-team/junit5/builds/219085282 3.7.0 soon sounds great! Edit: The cglib/AssertJ erros are gone with https://travis-ci.org/junit-team/junit5/builds/219085282#L900 -- moving on to the next ... issues. |
I think it has the same cause (cglib/cglib#94) as #927 which was fixed by updating to cglib |
I guess we can close this one then, @sormuras ? |
Sure. Looking forward to switch the dependency to AssertJ 3.7.0, soon. |
Summary
The JUnit 5 team is test-driving on Java 9 the coming days (and weeks).
Our current build fails because of a "NoClassDefFoundError" pointing to the shaded cglib in AssertJ 3.6.2.
We had a similar problem with the Gradle Shadow Plugin using an out-dated ASM version to move/shade entities. It was related to https://bugs.openjdk.java.net/browse/JDK-8174868
Log
https://travis-ci.org/junit-team/junit5/builds/219055181#L952
Solution?
Update Shade plugin you use to shade cglib and asm?
I'll try to generate a better stacktrace to pin-point the underlying error causing initialization of class
org.assertj.core.internal.cglib.proxy.Enhancer
to fail.The text was updated successfully, but these errors were encountered: