Difference between Gradle and Maven? [closed]

Solution 1:

You can think of Gradle as goodness of Ant and Maven put together minus the noise of XML. And scriptability with groovy is very big plus.

• Gradle gives you conventions but still gives you power to override them easily.
• Gradle build files are less verbose as they are written in groovy.
• It provides very nice DSL for writing build tasks.
• Has lot of good plugins and vibrant ecosystem

When to use Gradle and When to use Maven ?

Almost everywhere for creating java/groovy project. The build files are much terse.

With Google choosing Gradle as the new build system for Android SDK and mature libraries like Spring, Hibernate, Grails, Groovy etc. already using it to power their builds, there is no doubt that Gradle is becoming de-facto build system for the Java ecosystem.

Solution 2:

Gradle is the next evolutionary step in JVM-based build tools. It draws on lessons learned from established tools like Ant and Maven and takes their best ideas to the next level. Following a build-by-convention approach, Gradle allows for declaratively modeling your problem domain using a powerful and expressive Domain-Specific Language (DSL) implemented in Groovy instead of XML. As Gradle is a JVM native, it allows you to write custom logic in the language you are most comfortable with, be it Java or Groovy

For more information here: Next generation builds with Gradle