We are already looking forward to the Gradle 1.6 release.
Some of the key features we are tackling include:
- Provide an incremental build API to enable tasks to query what has changed in regard to its inputs and outputs. Work has already started in master. - Extend the Tooling API to capture the need of Android projects to enable better IDE integration. Work has already started in master. - Starting work on the Gradle Plugin Portal to improve the experience of publishing and using 3rd party plugins with Gradle. - The Gradle Bootstrap plugin will be polished and released as an incubating feature, allowing automatic POM conversion for simple Maven projects. Work has already started in master. - Make it easy for to produce multiple outputs per source set, such as different variants for an Android application, or libraries targeting different runtimes (eg Groovy-1.8 and Groovy-2.1). See the design doc. Work has already started in master. - The current ‘Jetty’ plugin is limited in scope and ability. We plan to commence work on a full-featured ‘Gradle Deployment Plugin’ backed by Arquillian. - Add a JaCoCo Code Coverage plugin to the Gradle Core. Work has already started in master. - Support for JUnit categories. Work has already started in master. - Provide a richer DSL for describing task dependencies. For example you will be able to define that if two tasks are going to be executed, one should run after the other, without creating a hard dependency between the two tasks.
We’ll also be tackling some bug fixes:
The number of community contributions we receive for Gradle continues to increase. In 1.6 we’ll be working to incorporate more of the pull requests we get from our fantastic community members. We are very grateful to everyone who contributes, from small documentation fixes to major new plugin developments.
Of course, we may not find the time to do all of the above, and if time allows there is plenty more we’d like to tackle.
Several of the features and bug fixes are in progress and some are already functional. We work hard on maintaining backward compatibility, so why not try out the latest Gradle Nightly instead of waiting for Gradle 1.6. We update all of our documentation as we go, so you can always see what’s been completed in the Gradle Nightly Release Notes. Your early feedback would be most appreciated.