The Gradle workforce has launched Gradle 8.0 that includes a discount within the construct period and an improved Kotlin DSL that helps Kotlin 1.8 and Java 11 options within the construct scripts.
Kotlin DSL, first launched in 2018, could also be used as a substitute for the Groovy DSL and gives improved content material help, refactoring and documentation in supported IDEs equivalent to IntelliJ, Eclipse, Apache NetBeans and Visible Studio Code. The newest launch permits .gradle.kts scripts to make use of Java 11 options as an alternative of Java 8.
An interpreter is now used for the declarative plugins {} block inside .gradle.kts scripts which reduces the compilation time by about 20%. Model catalog aliases for plugins, equivalent to alias(libs.plugins.mavenPublish), and type-safe plugin declarations, equivalent to `my-plugin`, should not but supported by the interpreter.
The embedded Kotlin was upgraded to 1.8.10 and the Kotlin DSL now helps the Kotlin API Degree 1.8 as an alternative of 1.4. Gradle 8 helps Kotlin Gradle Plugin 1.6.10 and newer, nevertheless a decrease Kotlin language model could be used, with out assist, by altering the language model and API model setting contained in the Kotlin compile process. Gradle 8 helps Android Gradle Plugin 8 and newer, or 7.3 and newer, when specifying the property: android.experimental.legacyTransform.forceNonIncremental=true.
Gradle now makes use of the listing hierarchy of included builds to forestall conflicts. Contemplate, for instance, the next listing format:
settings.gradle
levelOneDirectory
settings.gradle
levelTwoDirectory
settings.gradle
Beforehand, the extent levelTwoDirectory listing could possibly be compiled with gradle :levelTwoDirectory:compileJava, however now it ought to be compiled with gradle :levelOneDirectory:levelTwoDirectory:compileJava.
Duties of a buildSrc construct could now be run straight on the command line. For instance, gradle buildSrc:construct could also be used to run the construct process within the buildSrc construct. The brand new launch permits the buildSrc to embrace different builds by defining the pluginManagement {includeBuild(anotherBuildDirectory)} or includeBuild(anotherBuildDirectory) within the buildSrc/settings.gradle.kts or buildSrc/settings.gradle settings scripts. Checks for buildSrc are now not executed mechanically because the construct process is now not run.
The Configuration cache is an incubating characteristic to cut back the construct time by caching the results of the configuration section and utilizing the cache of subsequent builds. Gradle recommends beginning with caching easy duties first and, if profitable, attempt extra superior duties. By default, the cache is disabled however it might be enabled with the gradle --configuration-cache command of by including the org.gradle.unsafe.configuration-cache=true property to the gradle.properties file. This launch mechanically runs duties in parallel from the primary construct each time the configuration cache is enabled.The retention interval could now be configured, with a purpose to cleanup the cache in Gradle person dwelling after a certain quantity of days:
beforeSettings { settings ->
settings.caches {
downloadedResources.removeUnusedEntriesAfterDays = 45
}
}
The string format of JavaVersion used for sourceCompatibility and targetCompatibility now not incorporates the 1. prefix for Java 9 and newer. Gradle 8.0 helps Java variations 1.8, 9, 10 and 11 as an alternative of the Gradle 7.6 equivalents 1.8, 1.9, 1.10 and 11.
Launch 8.0.1 is the primary patch launch and the Gradle workforce recommends utilizing the newest minor model. The GitHub releases web page lists all of the obtainable variations.
The newest Gradle launch could also be put in by way of SDMAN! with the sdk set up gradle 8.0.1 command, by way of Homebrew with the brew set up gradle command or as a ZIP file by way of the Gradle Releases web page.
Gradle recommends working the gradle assist --scan command and viewing the deprecations part of the report earlier than upgrading. After that, the plugins ought to be up to date and, lastly, the gradle wrapper --gradle-version 8.0.1 command could also be used to replace the applying to Gradle 8.0.1. The Troubleshooting Builds information could also be used to resolve construct points. Extra data on upgrading an software from Gradle 7.0 to eight.0 could be discovered within the person information.
Gradle now shows an error, as an alternative of a warning, when utilizing the finalizedBy, mustRunAfter or shouldRunAfter strategies. Invalid Java toolchain configurations and automated downloads with out offering repositories now lead to an error, which can be resolved by following the person guide.
Gradle 8 eliminated the --add-opens argument to open JDK modules, java.base/java.util and java.base/java.lang , for Gradle staff. This implies the employees, by default, can now not use the reflection performance from the JDK internals. Warnings and errors displayed by instruments, extensions and plugins could be resolved by updating them.
Configuring the take a look at framework after specifying the take a look at choices now produces an error:
take a look at {
choices {
}
useJUnitPlatform()
}
Which can be resolved by utilizing the JVM Check Suite Plugin, or by configuring the take a look at framework earlier than specifying the take a look at choices:
take a look at {
useJUnitPlatform()
choices {
}
}
Varied API’s, strategies and options have been eliminated and the whole record of adjustments, in regards to the newest launch, could be discovered within the Gradle 8.0 Launch Notes.
