The Gradle team is excited to announce Gradle 6.5-milestone-2.
This release features 1, 2, ... n, and more.
We would like to thank the following community contributors to this release of Gradle: Cristian Garcia, fransflippo, Victor Turansky, Gregor Dschung, Roberto Perez Alcolea, kerr, and Erhard Pointl.
Switch your build to use Gradle 6.5-milestone-2 by updating your wrapper:
./gradlew wrapper --gradle-version=6.5-milestone-2
See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.5-milestone-2.
For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.
Gradle 6.5 now supports using a org.gradle.api.provider.Provider when adding dependencies.
For example:
dependencies {
// Version of Guava defaults to 28.0-jre but can be changed via Gradle property (-PguavaVersion=...)
def guavaVersion = providers.gradleProperty("guavaVersion").orElse("28.0-jre")
api(guavaVersion.map { "com.google.guava:guava:" + it })
}
This is useful for plugin authors that need to supply different dependencies based upon other configuration that may be set by the user.
Tooling API clients can now use a new method from GradleConnector to asynchronously cancel all Tooling API connections without waiting for the current build to finish.
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.
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 see gradle.org/contribute.
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.