This message was deleted.

If you need to use a plugin that requires Java 17, you cannot use toolchains for that, you have to actually run Gradle with Java 17.

Thanks. This also affects project plugins, doesn't it?

Yes, I said "a plugin". 🙂

Yes :) Okay, but then I find the release notes ambiguous: https://github.com/gradle/gradle/blob/v8.0.0-RC1/subprojects/docs/src/docs/release/notes.md#precompiled-script-plugins-now-use-the-configured-java-toolchain

This is different: this is for compiling the plugins, not for consuming them (and the release notes quite clearly say it).

In your case the section right above is of interest https://github.com/gradle/gradle/blob/v8.0.0-RC1/subprojects/docs/src/docs/release/notes.md#enhanced-script-compilation-to-use-the-gradle-jvm-as-kotlin-jvm-target

I always add something like this to make it fail with a clear message when I run into this situation.

buildscript {

if (!JavaVersion.current().java17Compatible) {

throw new GradleException("Gradle must be launched with Java 17 or greater. Set JAVA_HOME.")

}

}