Gradle 3.5 RC1 is now available
The Gradle team is pleased to announce Gradle 3.5.
First and foremost, we’re excited to announce the new Build Cache! Beyond incremental builds, Gradle can save time by reusing outputs from previous executions of a task, resolving them locally or remotely. We’ve worked hard to ensure many built-in tasks are cacheable and safe to try; however, this feature should not be used in production without fully understanding its current limitations, so it is not enabled by default.
We have been testing this feature at scale for quite some time on the Gradle build itself and with enterprise partners, and the feedback has been very positive. While this feature is incubating, we are improving the user experience, documentation, and debuggability so that everyone can enable the Build Cache eventually.
We would like your feedback. Please read the Build Cache user manual, try it in non-critical environments, and submit GitHub issues with build scans if you encounter problems.
Next, we lamented that sometimes Gradle console output did not show all work-in-progress during a build (especially with --parallel), so we’ve developed brand new console output!
Gradle Script Kotlin v0.8.0 (included in the distribution) is a major step forward in
usability. It brings a more consistent DSL, convenient and type-safe access to contributed project extensions and conventions, much better error reporting, bug fixes and, of course, the latest and greatest Kotlin release.
Finally, plugin resolution rules give you tighter control over how plugins are resolved through the new pluginManagement {} block.
We hope you will build happiness with Gradle 3.5, and we look forward to your feedback via Twitter or on GitHub.
Upgrade Instructions
Switch your build to use Gradle 3.5 RC1 quickly by updating your wrapper properties:
./gradlew wrapper --gradle-version=3.5-rc-1
Standalone downloads are available at https://gradle.org/release-candidate.
Reporting Problems
If you find a problem with Gradle 3.5 RC1, 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.