-
Notifications
You must be signed in to change notification settings - Fork 64
NoSuchMethodError 'boolean java.lang.CharSequence.isEmpty()' with JRE 11 #220
Comments
I've set the target version to 1.8, because according to Google that's what Android should support on an API level. Can you check if v1.71 of Kluent fixes this for you? I've had to rewrite/migrate some of the publishing stuff because the old maven plugin for publications was deprecated. I guess some things changed in between, as the |
Unfortunately that doesn't do it. I created a small reproducer. It runs the same simple test (asserting Interestigly You can verify this in the action tab. |
Thank you for the repro! I'll investigate further :) |
The conclusion is, that how the current build project is set up, that the JVM specific APIs to compile against are just picked up from JAVA_HOME (the JVM Gradle is started with), instead of the different ways to specify the target version. Using With #223 that should be no issue in the future anymore. The workaround from #224 is to remind to start the build with Java 8 when publishing artifacts. |
1.72 should show up in mavencentral at any moment, you can then test again :) |
Thanks for the quick release of kluent-1.70 which solved my issues with java 11 in one project. Unfortunately, there was more lurking behind the wall, only found in another project:
kluent-1.70 fails to run
Charsequence.shouldBeEmpty()
when run on jre 11.Stacktrace
If I run the test with java 17, the test succeeds.
Might setting source and/or target to
1.6
incommon
be related. (see here)The text was updated successfully, but these errors were encountered: