Gradle Release Notes

Version 8.0-rc-2

The Gradle team is excited to announce a new major version of Gradle, 8.0. This major version has breaking changes; please consult the Gradle 7.x upgrade guide for guidance.

This release includes several improvements to the Kotlin DSL for increased performance. This includes an interpreter to skip the Kotlin compiler for declarative plugins and an upgrade to Kotlin API level 1.8.

The benefits of using included builds are now available with buildSrc, such as running buildSrc tasks directly, skipping tests, and including other builds with buildSrc.

Additionally, we have made enhancements to the configuration cache, like loading tasks from the cache entry and running tasks as isolated and in parallel on the first build, along with several bug fixes and other general improvements.

We would like to thank the following community members for their contributions to this release of Gradle: Abdul Rauf, Andrei Nevedomskii, aSemy, Björn Kautler, bodhili, Cédric Champeau, Christoph Dreis, Clara Guerrero Sánchez, David Marin Vaquero, David Morris, Denis Buzmakov, Dmitry Pogrebnoy, Dzmitry Neviadomski, Eliezer Graber, Eric Pederson, Fedor Ihnatkevich, Gabriel Rodriguez, Herbert von Broeuschmeul, Jeff, Jendrik Johannes, Korov, Marcono1234, Mariell Hoversholm, Matthew Haughton, Matthias Ernst, Michael Ernst, Michael Torres, Pankaj, prasad-333, RicardoJiang, Róbert Papp, Siddardha Bezawada, Stephen Topley, Victor Maldonado, Vinay Potluri, Xin Wang.

Table Of Contents

Upgrade instructions

Switch your build to use Gradle 8.0-rc-2 by updating your wrapper:

./gradlew wrapper --gradle-version=8.0-rc-2

See the Gradle 7.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 8.0-rc-2.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

New features and usability improvements

Kotlin DSL

Gradle's Kotlin DSL provides an alternative syntax to the traditional Groovy DSL with an enhanced editing experience in supported IDEs, with superior content assistance, refactoring, documentation, and more.

Improved script compilation performance

Gradle 8.0 introduces an interpreter for the declarative plugins {} blocks in .gradle.kts scripts that make the overall build time around 20% faster. Calling the Kotlin compiler for declarative plugins {} blocks is avoided by default.

To utilize this performance, ensure you are using the supported formats in the declarative plugins {} blocks, for example:

plugins {
    id("java-library")                               // <1>
    id("com.acme.example") version "1.0" apply false  // <2>
    kotlin("jvm") version "1.7.21"                   // <3>
  1. Plugin specification by plugin identifier string
  2. Plugin specification with version and/or the plugin application flag
  3. Kotlin plugin specification helper

Note that using version catalog aliases for plugins or plugin specification type-safe accessors is not supported by the plugins {} block interpreter. This support will be added in a later version.

In unsupported cases, Gradle falls back to the Kotlin compiler, providing the same performance as previous Gradle releases.

For more information on plugin syntax, read the documentation on constrained syntax.

Updated the Kotlin DSL to Kotlin API level 1.8

Previously, the Kotlin DSL used Kotlin API level 1.4. Starting with Gradle 8.0, the Kotlin DSL uses Kotlin API level 1.8. This change brings all the improvements made to the Kotlin language and standard library since Kotlin 1.4.0.

For information about breaking and non-breaking changes in this upgrade, visit the upgrading guide.

Enhanced script compilation to use the Gradle JVM as Kotlin JVM target

If your team is using e.g., Java 11 to run Gradle, this allows you to use Java 11 libraries and language features in your build scripts.

Previously, the compilation of .gradle.kts scripts always used Java 8 as the Kotlin JVM target. Starting with Gradle 8.0, it now uses the version of the JVM running the build.

Note that this doesn't apply to precompiled script plugins, see below.

Precompiled script plugins now use the configured Java Toolchain

Previously, the compilation of precompiled script plugins used the JVM target as configured on kotlinDslPluginOptions.jvmTarget. Starting with Gradle 8.0, it now uses the configured Java Toolchain, or Java 8 if none is configured.

See the kotlin-dsl plugin manual for more information on how to configure the Java Toolchain for precompiled script plugins and the migration guide for more information on changed behaviour.

Improvements for buildSrc builds

This release includes several improvements for buildSrc builds to behave more like included builds. Included builds are an alternative way to organize your build logic to separate project configurations to better utilize incremental builds and task caching. Now they offer the same benefits.

Run buildSrc tasks directly

It is now possible to run the tasks of a buildSrc build from the command-line, using the same syntax used for tasks of included builds. For example, you can use gradle buildSrc:build to run the build task in the buildSrc build.

For more details, see the user manual

buildSrc can include other builds

The buildSrc build can now include other builds by declaring them in buildSrc/settings.gradle.kts or buildSrc/settings.gradle. You can use pluginsManagement { includeBuild(someDir) } or includeBuild(someDir) in this settings script to include other builds in buildSrc.

For more details, see the user manual

Tests for buildSrc are no longer automatically run

When Gradle builds the output of buildSrc it only runs the tasks that produce that output. It no longer runs the build task. In particular, this means that the tests of buildSrc and its subprojects are not built and executed when they are not needed.

You can run the tests for buildSrc in the same way as other projects, as described above.

Init scripts are applied to buildSrc

Init scripts specified on the command-line using --init-script are now applied to buildSrc, in addition to the main build and all included builds.

For more details, see the user manual

Configuration cache

The configuration cache improves build time by caching the result of the configuration phase and reusing this for subsequent builds. This is an incubating feature that can significantly improve build performance.

Improved configuration cache for parallelism on the first run

Configuration cache now enables more fine-grained parallelism than using the --parallel flag. Starting in Gradle 8.0, tasks run in parallel from the first build when using the configuration cache. These tasks are isolated and can run in parallel.

When the configuration cache is enabled and Gradle can locate a compatible configuration cache entry for the requested tasks, it loads the tasks to run from the cache entry and runs them in isolation. Isolated tasks can run in parallel by default, subject to dependency constraints.

When Gradle cannot locate a configuration cache entry to use, it runs the configuration phase to calculate the set of tasks to run and then stores these tasks in a new cache entry. Gradle then loads immediately the saved state and runs the build based on the loaded state. There are some additional advantages to this new behavior:

This consistent behavior for cache miss and cache hit builds can help people migrating to use the configuration cache, as more problems can now be discovered on the first (cache miss) build.

For more details, see the user manual.

Improved compatibility with core plugins

The gradle init command can be used with the configuration cache enabled.

The ANTLR plugin and Groovy DSL precompiled scripts are now compatible with the configuration cache.

The current status of the configuration cache support for all core Gradle plugins can be found in the configuration cache documentation.

Java Toolchains improvements

Updated toolchain download repositories

Gradle 7.6 introduced toolchain repositories for increased flexibility. In Gradle 8.0, there is no longer a default toolchain provisioner. You have to declare at least one Java Toolchain repository explicitly. This can be done via toolchain repository plugins, like the Foojay Toolchains Plugin:

plugins {
    id("org.gradle.toolchains.foojay-resolver-convention") version("0.4.0")

For more details, see the user manual.

General improvements

Improved Gradle user home cache cleanup

Previously, cleanup of the caches in Gradle user home used fixed retention periods (30 days or 7 days, depending on the cache). These retention periods can now be configured via the settings object in an init script in Gradle user home.

beforeSettings { settings ->
    settings.caches {
        downloadedResources.removeUnusedEntriesAfterDays = 45

Furthermore, it was previously only possible to partially disable cache cleanup via the org.gradle.cache.cleanup Gradle property in Gradle user home. Disabling cache cleanup now affects more caches under Gradle user home and can also be configured via the settings object in an init script in Gradle user home.

For more details, see the user manual.

Enhanced warning modes all and fail are now more verbose

Before Gradle 8.0, warning modes that were supposed to print all warnings were printing only one for each specific warning message. This resulted in some missing warning messages. For example, if there were two warnings with the same message, but originating from different steps of the build process (i.e., different stack traces), only one was printed.

Now one gets printed for each combination of message and stack trace. This result is more verbose, but also more complete.

For more details, see the user manual.

Improved dependency verification metadata

Dependency verification metadata helps keep your project secure by ensuring the dependency being used matches the checksum of that dependency. This metadata is located in an XML configuration file and now accepts a reason attribute. This reason attribute allows for more details on why an artifact is trusted or why a selected checksum verification is required for an artifact directly in the verification-metadata.xml.

The following nodes with dependency verification metadata file verification-metadata.xml now support a reason attribute:

A reason is helpful to provide more details on why an artifact is trusted or why a selected checksum verification is required for an artifact directly in the verification-metadata.xml.

For more details, see the user manual.

Improved dependency verification CLI

To minimize the number of times CI builds communicate with key servers, we use a local keyring file. This file should be frequently exported to remain accurate. There is no longer a need to write verification metadata when exporting trusted keys, simplifying the process.

You can now use the export-keys flag to export all already trusted keys:

./gradlew --export-keys

There is no longer a need to write verification metadata when exporting trusted keys.

For more details, see the user manual.

Code quality plugin improvements

CodeNarc plugin detects the Groovy runtime version

CodeNarc performs static analysis for Groovy projects. It now publishes separate versions for use with Groovy 4. Gradle still currently ships with Groovy 3.

To ensure future compatibility, the CodeNarc Plugin now automatically detects the appropriate version of CodeNarc for the current Groovy runtime.

You can still explicitly specify a CodeNarc version with the toolVersion property on the CodeNarcExtension.

PMD and CodeNarc tasks now execute in parallel by default

The PMD plugin performs quality checks on your project’s Java source files using a static code analyzer. It now uses the Gradle worker API and JVM toolchains. This tool now performs analysis via an external worker process, and therefore its tasks may now run in parallel within one project.

In Java projects, this tool will use the same version of Java required by the project. In other types of projects, it will use the same version of Java that is used by the Gradle daemon.

For more details, see the user manual.

Promoted features are features that were incubating in previous versions of Gradle but are now supported and subject to backwards compatibility. See the User Manual section on the “Feature Lifecycle” for more information.

The following are the features that have been promoted in this Gradle release.

The following type and method are now considered stable:

Fixed issues

Known issues

Known issues are problems that were discovered post release that are directly related to changes made in this release.

External contributions

We love getting contributions from the Gradle community. For information on contributing, please see

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.