Gradle Release Notes

Upgrade instructions

Switch your build to use Gradle 9.10.0-20261102002359+0000 by updating the wrapper in your project:

./gradlew :wrapper --gradle-version=9.10.0-20261102002359+0000 && ./gradlew :wrapper

See the Gradle 9.x upgrade guide to learn about deprecations, breaking changes, and other considerations when upgrading to Gradle 9.10.0-20261102002359+0000.

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

New features and usability improvements

Isolated Projects

Isolated Projects is an incubating performance feature that safely runs project configuration in parallel, significantly reducing configuration time in many scenarios, including IDE sync and CI builds.

Configuration Cache improvements

Gradle provides a Configuration Cache that improves build time by caching the result of the configuration phase and reusing it for subsequent builds.

Test reporting and execution

Gradle provides a set of features and abstractions for testing JVM code, along with test reports to display results.

CLI, logging, and problem reporting

Gradle provides an intuitive command-line interface, detailed logs, and a structured problems report that helps developers quickly identify and resolve build issues.

Rich console improvements

In the rich console, the work in progress is shown on worker lines, below the progress bar. In this release, worker lines cover more of the build and tell you more about each piece of work.

Before, some work had no worker line of its own. This work is now shown on worker lines:

• Before the tasks: the check of the configuration cache fingerprint, the projectsLoaded, projectsEvaluated and taskGraph.whenReady listeners, and the generation of version catalog and project accessors.
• After the last task: flow actions, the close() method of build services, and the write operations for dependency locks and dependency verification metadata.
• During a task: the work actions of the task, such as the ones submitted with the Worker API. When a task has more than one work action, each work action in progress is shown on its own line. The number of completed work actions is shown on the line of the task, as for test tasks.

On most lines of an included build or of a buildSrc build, the path of the build is put before the work, as in > :lib > Evaluating settings. Before, no build was shown for the settings, the loading of the projects and the init scripts of an included build or of a buildSrc build.

More information is also shown on each worker line:

• After 10 seconds of work on a line, the time since the start of this work is shown at the end of the line. For a test task, the time of the current test class is shown. With this time, you can see the difference between a blocked task and a new task.
• When a line is too long for the console, the middle of the line is cut. The task path at the start and the end of the line are kept. Before, the end of the line was cut, and the name of a test class was often lost:

Before  > :services:payments:test > Executing test com.example.payments.retry.SlowNetwo
After   > :services:payments:test > ...retry.SlowNetworkRetryIntegrationTest  25s

On the Linux text console, the progress bar is now drawn with ASCII characters. The fonts of this console do not have the partial block characters of the Unicode bar, so a replacement character was shown at the edge of the filled part. With --console-unicode=enable, the Unicode bar is still used.

See the Rich console section in the Gradle User Manual for more details.

Build authoring improvements

Gradle provides rich APIs for build engineers and plugin authors, enabling the creation of custom, reusable build logic and better maintainability.

Dependency management enhancements

Gradle provides a flexible dependency management engine for declaring, resolving, and verifying the dependencies your build needs.

Platform and toolchain management

Gradle provides comprehensive support for JVM languages, featuring automated Toolchains for seamless JDK management.

Core plugin and plugin authoring enhancements

Gradle provides a comprehensive plugin system, including built-in Core Plugins for standard tasks and powerful APIs for creating custom plugins.

Security and infrastructure

Gradle provides robust security features and underlying infrastructure to ensure that builds are secure, reproducible, and easy to maintain.

Tooling and IDE integration

Gradle provides Tooling APIs that facilitate deep integration with modern IDEs and CI/CD pipelines.

Performance improvements

Gradle continuously improves build performance through caching, parallelism, and reduced overhead across all phases of the build.

General improvements

Gradle provides various incremental updates and performance optimizations to ensure the continued reliability of the build ecosystem.

Promoted features

Promoted features are features that were incubating in previous versions of Gradle but are now supported and subject to backward 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.

Documentation and training

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 gradle.org/contribute.

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 if 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.