NoSuchMethodError 'boolean java.lang.CharSequence.isEmpty()' with JRE 11 about kluent HOT 5 CLOSED

1.72 should show up in mavencentral at any moment, you can then test again :)

from kluent.

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 .module files are completely new to me.
Maybe I've implicitly built against Java 11 in the past, but I'm pretty sure that would have broke Android users, at least at that time.

from kluent.

Unfortunately that doesn't do it.

I created a small reproducer. It runs the same simple test (asserting "".shouldBeEmpty() and "x".shouldNotBeEmpty() - both expected to pass) once with jdk17 and once with jdk11.

Interestigly shouldNotBeEmpty() passes in both scenarios. However, shouldBeEmpty() fails on JDK 11 but passes on JDK 17.

You can verify this in the action tab.

from kluent.

Thank you for the repro!
I've fiddled a bit with the build scripts and still can't figure out where the issues is. The assertions you're having the issue with is over a year old, so I must have messed something up in the gradle project.

I'll investigate further :)

from kluent.

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 jvmToolchain is currently not possible, as that would need an update to the kotlin gradle plugin, which would mean that some things the build currently does break.

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.

from kluent.