Gradle 3.1 is now available
Multi-project builds are a powerful feature with one significant constraint: the projects have to be in the same directory hierarchy. This doesn’t help if you want to work on code across multiple repositories, for example if you’re trying to fix a bug in a third-party open-source library that one of your projects depends on.
Gradle 3.1 now supports this scenario with the introduction of Composite Builds for all users. It’s hard to understate just how important this feature is as it provides a whole new way of organizing your projects and builds. There is more work to be done in this area and the feature is currently incubating, but we encourage you to try it out and give us your feedback!
Incremental Build is a similar feature in terms of impact and this release improves the control you have over its up-to-date checks. You can read about the details in the release notes.
As with many previous Gradle releases, you will also benefit from some performance improvements, this time in the form of faster dependency resolution. From testing, Android users specifically could see up to a 50% reduction in configuration and Android Studio sync time.
Build cancellation has improved when using the Daemon. Cancelling a build with Ctrl-C after the first build no longer terminates the Gradle Daemon.
Our Play Framework and Kotlin build script users will also be happy as 3.1 now has (limited) support for Play 2.5.x and the Kotlin build script support gets a more fully-featured syntax for declaring dependencies and faster code completion.
Finally, be sure to check out the potential breaking changes in case they affect you.
Check the 3.1 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.1 quickly by updating your wrapper properties:
./gradlew wrapper --gradle-version=3.1
Standalone downloads are available at https://gradle.org/gradle-download.
If you find a problem with Gradle 3.1, please create a new topic in the Bugs category of the Gradle Forum. Be sure to include which operating system you are using, the version of Gradle you upgraded from and any steps you have found that reproduces your problem.