This is a backport release, Gradle 6.9.4.
This is the fourth patch release for Gradle 6.9.
It fixes the following issues:
Issues fixed in the third patch release:
Issues fixed in the second patch release:
Issues fixed in first patch release:
We recommend users upgrade to 6.9.4 instead of 6.9.
Given the context of the Log4Shell vulnerability, make sure you take a look atour blog post on this topic.
This release features bugfixes and other changes that werebackported from Gradle 7.x to Gradle 6.x.
We would like to thank the following community contributors to this release of Gradle:Ståle Undheim,Fodor Zoltan
Switch your build to use Gradle 6.9.4 by updating your wrapper:
./gradlew wrapper --gradle-version=6.9.4
See theGradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.9.4.
NOTE: Gradle 6.9 has hadtwo patch release, which fixes several issues from the original release. We recommend always using the latest patch release.
For Java, Groovy, Kotlin and Android compatibility, see thefull compatibility notes.
This release does not supportrunning Gradle with JDK 16, but you can useJava toolchains to request Java 16 and compile your project.
Until now, theplugins { } block only supported fixed versions for community plugins. Allversion string notations Gradle supports are now accepted, including+ orlatest.release.
We recommend using theplugins {} block for applying plugins using Gradle 7. The oldapply plugin: mechanism will be deprecated in the future.
Note that dynamic versions will introduce non-deterministic behavior to your build process and should be used judiciously. You can usedependency locking to save the set of dependencies resolved when using dynamic versions.
Previous Gradle versions were able to run on new Macs with Apple Silicon processors with some disadvantages:
With this release, every feature is now supported using a native ARM JDK. If you're using a new Mac with Apple Silicon, you should use Gradle with a native ARM JDK for optimal performance.
Please refer to the list below for all issues backported from Gradle 7.0.
Known issues are problems that were discovered post release that are directly related to changes made in this release.
We love getting contributions from the Gradle community. For information on contributing, please seegradle.org/contribute.
If you find a problem with this release, please file a bug onGitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use theforum.
We hope you will build happiness with Gradle, and we look forward to your feedback viaTwitter or onGitHub.