[Gradle is] a more modern version of open source build tools like Ant and Maven. Whereas the build config was XML files which were tedious and error prone, the modern DSL usage of Groovy to write these build files is a great advancement. Also these config files can be inherited from top level to each associated project.
Companies can't remove reviews or game the system. Here's why
Without the use of Gradle, we have done direct integration with the APIs. This has not worked very well in the case of Android as there are a lot of packaging related actions that Gradle directly takes as part of the plugin. This decision to use Gradle was an easy one.
Maven is a much more mature build tool. The community behind maven plugins has continued to grow over time, and there are several mature products that continue to receive support. Gradle can use some of these features, but appears to be losing steam over time. The effort to build a maven project can be a little more up front than Gradle, but overall it provides a much better experience.
I have participated in a variety of build environments, from basic shell scripts, to ant, and to maven. All of these tools have a place, sometimes perhaps in legacy code. But moving forward, I would never go back to other more primitive tools (never say never...). The more I learn and use Gradle, the more of an advocate I become.
Maven is the most popular alternative to Gradle, in my opinion. I think that both have their advantages and disavantages so I would advise people to scan through the documentation and example applications of both tools and choose according to their needs and limitations.
Gradle is an open source build system.
What is Gradle?