You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we test on two platforms - jdk11 and jdk17. But once #1304 gets figured out, we could run our build on Java 17, up the source level to 17 for tests, and use Gradle toolchain to run tests against jre 11 + 17.
That might be too complicated, and java 11 LTS reaches end of life in 2026 which will be here before we know it anyway. But if you made a PR that
preserved the existing test matrix
but always used java 17 as the build jre
compiled bytecode to java 11 for the jars
compiled bytecode to java 17 for the tests
That would be welcome and quickly merged!
The text was updated successfully, but these errors were encountered:
It would be really convenient if our tests could use multiline string literals. Then we could remove some of this cuteness
spotless/testlib/src/main/java/com/diffplug/spotless/ResourceHarness.java
Lines 184 to 186 in aa78b56
spotless/plugin-gradle/src/test/java/com/diffplug/gradle/spotless/ConfigurationCacheTest.java
Lines 50 to 61 in aa78b56
Right now we test on two platforms - jdk11 and jdk17. But once #1304 gets figured out, we could run our build on Java 17, up the source level to 17 for tests, and use Gradle toolchain to run tests against jre 11 + 17.
That might be too complicated, and java 11 LTS reaches end of life in 2026 which will be here before we know it anyway. But if you made a PR that
That would be welcome and quickly merged!
The text was updated successfully, but these errors were encountered: