Gradle build tool improves usablity
For version 1.1 of the Gradle build tool, the developers have focused on improving usability, fixing bugs and preparing the ground for the next generation of the cross-platform tool for building, testing and integrating projects in a Java environment. Gradle can be thought of as a replacement for Ant or Maven. Improvements in the Maven integration, dependency management and OSGi support are top of the list of issues resolved, but a number of new features have been added.
These include more detailed and fine-tuneable logging of tests that can include information on where an assertion failed and filterable stack traces. The test and quality reports are now presented as URLs to make them clickable in URL-aware terminals. The Tooling API provides module information for external dependencies, a first step to providing a more comprehensive dependency system. Users of Maven who migrate to Gradle will find that Gradle now honours settings in
$M2_HOME/conf/settings.xml. Other enhancements include publication of SHA1 checksums to Ivy repositories and support for HTTP digest authentication when doing dependency resolution. Deprecations and other changes from Gradle 1.0 are listed in the release notes.
For Gradle 1.2, the developers are working on parallel builds, an update and migration plugin and better dependency reporting. A forum posting also gives details for future releases in terms of frequency, design and quality. Gradle 1.1 is available to download as source or binary from the project's downloads page, along with documentation. The Apache 2.0 licensed Gradle can also be found on GitHub.