Set release flag manually instead of using Gradle toolchains

mhalbritter · mhalbritter · commit f6a8d02053c7 · 2022-08-22T10:53:40.000+02:00
Using the toolchains will lead to Gradle always using a JDK 11 if
available, which is not what we want. We want the source code to be
Java 11 compatible, and then run the tests on GraalVM 11 and 17.
diff --git a/tests/tck-build-logic/src/main/groovy/org.graalvm.internal.tck.gradle b/tests/tck-build-logic/src/main/groovy/org.graalvm.internal.tck.gradle
@@ -20,10 +20,8 @@ repositories {
     mavenCentral()
 }
 
-java {
-    toolchain {
-        languageVersion = JavaLanguageVersion.of(11)
-    }
+tasks.withType(JavaCompile) {
+    options.release = 11
 }
 
 TestUtils.locateRepoDirs(project) // Find relevant directories for the test harness.

Original file line number	Diff line number	Diff line change
`@@ -20,10 +20,8 @@ repositories {`
`20`	`20`	`mavenCentral()`
`21`	`21`	`}`
`22`	`22`
`23`		`-java {`
`24`		`- toolchain {`
`25`		`- languageVersion = JavaLanguageVersion.of(11)`
`26`		`- }`
	`23`	`+tasks.withType(JavaCompile) {`
	`24`	`+ options.release = 11`
`27`	`25`	`}`
`28`	`26`
`29`	`27`	`TestUtils.locateRepoDirs(project) // Find relevant directories for the test harness.`