Gradle 3.3 is now available
This release of Gradle makes the gradle tasks report much faster for medium-to-large projects. By default, gradle tasks will now only display tasks which have been assigned a task group.
For example, execution time was reduced from 554 seconds to 3 seconds on our perf-enterprise-large benchmark project — over 100x faster!
See the technical details on how and why this change was made in the full release notes.
It is now possible to compile native applications using Visual Studio 2015. Gradle will locate the Universal C Runtime required by the Visual C++ toolchain.
Kotlin build script support has further improved with significantly faster startup performance, increased API parity with Groovy-based build scripts, and better interoperability with Groovy plugins. See the gradle-script-kotlin v0.5.0 release notes for details.
Scala compilation startup time in large multi-project builds has been improved through enhancements to Gradle’s integration with the Zinc Scala compiler. In earlier versions of Gradle, builds with many Scala projects could timeout and fail when building in parallel.
Tooling API generates more progress events. This means that IDEs will show a much clearer picture of what Gradle is doing during the configuration phase, resolving dependencies, and using composite builds. Details and pictures in the full release notes.
The Gradle GUI has been deprecated and will be removed in Gradle 4.0. An IDE which provides a UI for Gradle — IntelliJ IDEA, Eclipse, or NetBeans, for example, is recommended.
Check the full 3.3 release notes for more information.
Upgrade Instructions
Switch your build to use Gradle 3.3 quickly by updating your wrapper properties:
./gradlew wrapper --gradle-version=3.3
Standalone downloads are available at Gradle | Installation.
Heads up: In addition, if you previously generated the wrapper with Gradle 3.2, re-run
./gradlew wrapperto avoid a misconfigured wrapper script.
Reporting Problems
If you find a problem with Gradle 3.3, 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.