Welcome to the October 2020 Gradle Build Tool newsletter.
This issue covers the news for the community, and the new releases of Gradle Build Tool, Gradle Enterprise, and Android Studio.
We started regularly sharing various #GradleTips on Twitter that we hope you’ll find useful. Follow us on Twitter to get them as well as other updates.
You can use the `because` clause to document why a specific dependency is needed in your project. The reason will also be visible in build scans and in the command-line dependency insight report. #GradleTips pic.twitter.com/pZR4XEppLx
— Gradle (@gradle) October 7, 2020
Gradle 6.7 has been released and is packed with new features and enhancements. As of this release, the file system watching feature that makes incremental builds faster is ready for production use. This release also brings Java toolchain support that makes it much easier to build JVM projects using a different version of Java than the one Gradle is running on. Running on and building with Java 15 is also supported. See release notes for details and information about other improvements in this release.
Gradle Enterprise 2020.4 has been released and ships with a number of highly anticipated features. Correlation and detection analysis of similar build failures makes it easy to identify whether a build failure is isolated or widespread. The improved fault tolerance for distributed testing decreases the disruptions caused by unreliable network environments. More build history can be retained than before thanks to more efficient build data storage. Configuring and administering a Gradle Enterprise installation is also now much more convenient. See release notes for details.
Android Studio 4.1 has been released. It brings a number of improvements including a faster feedback loop with “apply changes”. This is the first release that is compatible with Gradle’s experimental configuration cache](). However, we recommend that early adopters of configuration cache use the latest 4.2 [canary version to get all the latest bug fixes. See the blog post for details about this release.
See the Gradle Training webpage for an up-to-date list of all upcoming educational and training events.
If you have some news you’d like us to share in the next issue, use #gradle
on Twitter or send us an email with the details to newsletter@gradle.com.
Until next time!
—The Gradle Team
Gradle Inc. | 2261 Market Street #4081 | San Francisco, CA 94114
Privacy Policy | Unsubscribe