Pre-release
Pre-release

@cbeams cbeams released this Jun 9, 2016 · 23208 commits to master since this release

Assets 2

General Notes

This release is the first in a short series of milestones leading up to Gradle 3.0 GA. Its purpose is to gather feedback on each of the major changes listed below.

We encourage all Gradle users to give 3.0 M1 a try and let us know how it goes. See the Getting Started and Providing Feedback sections below for details.

For more information, please see the announcement blog post and detailed release notes.

New Features and Improvements

  • The Gradle Daemon is now enabled by default. The Gradle Daemon is a long-running background process that dramatically improves Gradle command line responsiveness and overall build times. Prior to this release, the daemon had been an opt-in feature, requiring users to enable it explicitly. Now the daemon is enabled by default, meaning it is no longer necessary to provide the --daemon option or to set the org.gradle.daemon property to true.
  • Gradle build scripts can now be written in Kotlin. Kotlin is a statically-typed programming language for the JVM with rich IDE support. This release introduces initial support for writing Gradle build scripts in Kotlin, enabling the use of autocompletion, quick documentation, refactoring and other key IDE features. See the announcement blog post and Gradle Script Kotlin 1.0 M1 release notes for complete details, samples and getting started instructions.

Caveats and Limitations

  • Features deprecated in the Gradle 2.x line have been removed. See the latest (Gradle 2.13) deprecation list for details.
  • Running Gradle on Java 6 is no longer supported. Gradle itself now requires Java 7 or better to run, but compiling project sources and running tests with Java 6 remains supported. See the cross-compilation for Java 6 section of the user guide for details.

Getting Started

The best way to try out 3.0 M1 is against a real-world project whose build you are already familiar with.

Set your Gradle wrapper version to 3.0-milestone-1 as follows:

$ cd $YOUR_GRADLE_PROJECT
$ gradle wrapper --gradle-version 3.0-milestone-1

Then run the wrapper to trigger download and installation:

$ ./gradlew --version
Downloading https://services.gradle.org/distributions/gradle-3.0-milestone-1-bin.zip
....................................................................................
....................................................................................
------------------------------------------------------------
Gradle 3.0-milestone-1
------------------------------------------------------------
[...]

Now continue to operate the build via the ./gradlew wrapper as you normally would and experiment with the new features as you go.

Providing Feedback

If you believe you've found an issue with Gradle 3.0 M1 or simply have a question about it, please:

  • Post a topic in the 3.0 M1 feedback category of the Gradle Forums
  • Paste the output of ./gradlew --version so we can see relevant OS and JDK information
  • Provide, if possible, a small example that reproduces the problematic behavior