Enterprise Integration Zone is brought to you in partnership with:

Ben is a writer, editor, coffee addict, beer snob, and music lover living in Cary, NC. He first became interested in computer hardware at a young age, and has built more than his fair share of desktop PCs over the years. He's a total device junkie and welcomes the coming age of the Internet of Things. His interest has since spread to tech media in general—in particular he writes about cloud technologies, middleware, DevOps, IoT, and enterprise architecture. He's easy to get a hold of, especially on Twitter, where he keeps an active presence. Get in contact to discuss all things software, whatever your favorite beer is, interesting tech topics... really, just talk about anything. Benjamin is a DZone Zone Leader and has posted 128 posts at DZone. You can read more from them at their website. View Full User Profile

Gradle 2.0 Release - Brings Backwards Compatibility, Memory Efficiency, and Higher Performance

07.07.2014
| 10498 views |
  • submit to reddit

 Gradle 2.0 came out last week, and it's a pretty big move from Gradle--the first major version update they've done. With the major release comes a baseline of backwards compatibility, and a significantly simplified codebase. They were able to simplify services by removing expired and redundant features and API. There's more details on the exact things that were removed and added in the official release notes. It's worth pointing out that the "Potential Breaking Changes" section is probably of particular use to a lot of readers.

A major focus of the version update was improving memory efficiency and performance, especially for large builds, which was successfully implemented. Due to the critical nature of performance in build systems, the Gradle team is going to focus extensively on performance and efficiency (especially in the build process) throughout the version 2.x cycle.

In addition to these major changes, they made some other alterations that they elaborated on:

In addition to the breaking changes of Gradle 2.0, the 2.0 release is business as usual with the steady evolution of Gradle via new and refined API and features. The move to Groovy 2.3.2 from Groovy 1.8 brings with it all of the new features added to Groovy in this time. There is now a public API for resolving “source” and “javadoc” JARs for JVM library components. The exposing of Ivy “Extra Info” attributes enables a new class of advanced dependency management use cases. It is now possible to use the SFTP protocol for dependency consumption without using custom Ivy resolvers. Maven POM profile support has also been improved through support for profile activation through absence of a system property.

For more information on the version changes, including information about v2's support of building native projects, refer to the release notes.