Gradle 3.2 RC1 is now available for testing
It’s a relatively quiet release this time around, but there are still plenty of reasons to upgrade.
Perhaps the most significant improvements are in the incremental build support, which now has better up-to-date checking for Java compilation, copying, and archiving. You can also have Gradle treat any task input as a classpath with the new
Users of Gradle’s native build support gain an important tool in this release. Many of you will be familiar with the
buildDependents task for classic multi-project builds. This is now available in native builds as well via new
buildDependents tasks. These are incredibly useful for determining whether your changes have adversely impacted anything that depends on them.
If you use an IDE and have a lot of dependencies in your build—particular dynamic ones—you may have experienced long import times. The underlying issue has been fixed in this release, resulting in significantly improved import times. One example enterprise build showed a 100-fold improvement!
Our users trialling the Kotlin build script support will be glad to hear that progress continues apace with support for multi-project builds. And it’s easier to try this feature on Windows now that a bug in compiling scripts on that platform has been fixed.
The last change we want to bring to your attention has been a long time coming and will affect a large number of builds: the shortcut syntax for declaring tasks (via
<<) has now been deprecated. The eagle-eyed among you will notice that the user guide examples have been updated to use
doLast() and we strongly recommend that you follow suit. This feature will be removed in Gradle 5.0! See the deprecations section of the release notes for more details.
Check the 3.2 RC1 release notes for more information. If no regressions are reported, a final release will typically follow in the next week.
Switch your build to use Gradle 3.2 RC1 quickly by updating your wrapper properties:
./gradlew wrapper --gradle-version=3.2-rc-1
Standalone downloads are available at https://gradle.org/release-candidate.