Gradle is build automation evolved. Gradle can automate the building, testing, publishing, deployment and more of software packages or other types of projects such as generated static websites, generated documentation or indeed anything else.
Gradle combines the power and flexibility of Ant with the dependency management and conventions of Maven into a more effective way to build. Powered by a Groovy DSL and packed with innovation, Gradle provides a declarative way to describe all kinds of builds through sensible defaults. Gradle is quickly becoming the build system of choice for many open source projects, leading edge enterprises and legacy automation challenges.
I have never felt comfortable with Maven.
The switch to Gradle made building fun again!
Here is my path to build nirvana
make -> ant -> ant+ivy > maven -> GRADLE
I've switched over all my builds from Ant and Maven to Gradle, and never regretted it. Most common things you want to do are built right into Gradle.
I have found that the documentation, while verbose, can be a bit of a maze, with a mix of user documentation, JavaDoc, and the "DSL guide", all linked together. The big issue is that what you can put in your build depends on what properties are exposed by what objects, and often that's determined by the implementation class provided by Gradle, not the interface class defined in the DSL. So you can run in circles until you stumble on your solution.
Like many projects, the docs focus on what you can do vs. common usages. Using Gradle effectively is an exercise in learning how to read and understand those docs.
That being said, Gradle is the best tool for builds, and the one that's easiest to extend. I've had bad experiences with other tools, but Gradle has yet to let me down.
A great powertool for pretty much any maintenance tasks you do with your project. A big advantage over Maven (and other only-declarative tools) is that Groovy is a real programming language so if Gradle doesn't do exactly what you want you can pretty easy make it as you'd like. It comes in handy when you want to craft some custom tasks (like code generating or so). It's really simple when compared to alternatives (read sbt).
More intuitive and powerful than Maven
Simply wonderful buildtool.
When all you have is Gradle
everything seems like a problem solved
Gradle provides all the benefits of Maven (build conventions, plugin ecosystem, dependency management, and nested builds) without the need for rigid adherence to arbitrary conventions. A greenfield Gradle project can benefit by sticking with defaults that are sensible and a brownfield project can create configuration customizations that will allow you to port virtually any build structure to Gradle with minimal effort.
Gradle's only weak points are where the build system is so flexible that at times it is hard to track where your changes mess with established documentation (in these cases you've sort of made your own bed so it's your own fault for getting so far off track). Most of the major IDE's support Gradle so the tooling is already there. Over all, Ithere is no other build system I would choose to start a new project with and there are very few legacy projects that wouldn't benefit from getting upgraded to a gradle build.