#Gradle versions install#

#Gradle versions install#

With toolchains support, Gradle can autodetect local JDKs and install missing JDKs that Gradle requires for the build. Use a JDK and a JRE that are different from the Gradle ones to run compilations, tests, and executables.Ĭompile and test code with a not-yet-released language version. Gradle 6.7 introduced Java toolchains support. When you use a custom JDK, note that kapt task workers use process isolation mode only, and ignore the property. The jdkHome compiler option is deprecated since Kotlin 1.5.30. If you need to change the JDK by some reason, you can set the JDK home with Java toolchains or the Task DSL to set a local JDK. Ignore – the plugin will skip the check and won't produce any messages.īy default, Kotlin compile tasks use the current Gradle JDK. Warning – the default value the Kotlin Gradle plugin will print a warning message. For example: the compileKotlin task has jvmTarget=1.8, and the compileJava task has (or inherits) targetCompatibility=15.Ĭontrol the behavior of this check by setting the .mode property in the adle file equal to: Different values of jvmTarget in the kotlin extension and targetCompatibility in the java extension cause incompatibility.

Main and test source set compile tasks are not related.įor such related tasks, the Kotlin Gradle plugin checks for JVM target compatibility. In the build module, you may have related compile tasks, for example: += 'src/main/myKotlin'Ĭheck for JVM target compatibility of related compile tasks