New and Noteworthy
Easier Ivy repositories.
It is now much easier to define an Ivy repository. Here's an example:
Compare this with how you used to define an Ivy repository:
Under the covers, Gradle will choose the appropriate repository implementation based on the URL patterns you have supplied. In particular, Gradle now works better for HTTP and HTTPS repositories:
- Gradle is now much more reliable when publishing large artifacts.
- Gradle now displays upload progress information. This is quite useful when publishing large artifacts.
Minor DSL Improvements
There is now an easier way to query for all the source directories of a source set. The allSource, allJava, allGroovy and allScala properties now have a srcDirs property. Here's an example:
Previously, you has to manually merge the source directories from the java, resources, groovy and scala source.
Tooling API
A new API is available to make it easier to integrate Gradle with tools such as IDEs, CI servers and other tools. The goal of this API is to provide a way to execute Gradle builds, and to query information about them, in a way that is independent of Gradle version. If you maintain some integration with Gradle, you should consider switching to use the tooling API.
Migrating from 1.0-milestone-2
Gradle 1.0-milestone-3 Breaking Changes
