Recs.
Updated
Specs
Pros
Pro Short scripts
Since Gradle does not use XML but it uses it's own DSL based on Groovy, Gradle scripts tend to be shorter than other build tools that use XML. Boilerplate code is also considerably small because it's DSL is designed to solve a specific problem: moving the software through its lifecycle starting from compilation into static analysis and testing, packaging and finally deployment.
Pro Dependency programming tool
Gradle is a dependency programming tool first and foremost. Gradle will make sure that all declared dependencies are properly executed for every random task that you execute in your setup. The code can be spread across many directories in any kind of file layout.
Pro IDEA integration
Gradle has full integration with Jetbrains IDEA.
IDEA understands multi-module Gradle builds and automatically maintains the IDEA modules within the project.
You also have the option to run unit tests with either the built-in JUnit/TestNG test runner, or delegate running the test to Gradle using the same visualization as the built-in runner.
Cons
Recommendations
Comments
Out of Date Pros + Cons
Con Can get slow for large builds
Since Gradle uses Groovy instead of XML for it's configuration scripts, it achieves a great deal of flexibility but unfortunately that comes with slower builds when the project gets large enough. This is because the entire Groovy script has to be recompiled for every build instead of simply being parsed.