What users are saying about

Apache Maven vs Gradle

Apache Maven
46 Ratings
Gradle
26 Ratings

Apache Maven

46 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.3 out of 100

Based on 46 reviews and ratings

Gradle

26 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8 out of 100

Based on 26 reviews and ratings

Likelihood to Recommend

Apache Maven

Building and automating packaging of software can be a challenging task. As the complexity of the project grows so do the dependencies on third-party artifacts. Using Maven we can define and manage the project structure centrally and it helps improve overall build times.

Read full review

Anonymous | TrustRadius Reviewer
Verified User
View all 9 answers on this topic

Gradle

Gradle is an ideal tool to build an application that is complex and/or distributed. It is well suited for builds that use a CI engine such as Jenkins or Bamboo, and a repository such as Artifactory.

Read full review

Dirce Richards | TrustRadius Reviewer
Dirce Richards
View all 8 answers on this topic

Pros

Apache Maven

  • Maven is useful in building Java applications.
  • Quick project setup, no complicated build.xml files, just a POM and go. Reduces the size of source distributions, because jars can be pulled from a central location.

Read full review

Anonymous | TrustRadius Reviewer
Verified User
View all 9 answers on this topic

Gradle

  • We use it as a build tool.
  • We build Java applications using this tool.
  • We also use Gradle to test our apps.

Read full review

Anonymous | TrustRadius Reviewer
Verified User
View all 8 answers on this topic

Cons

Apache Maven

  • POM file in XML is quite messy, especially with a big project.
  • Dependency management with a local cache sometimes causes conflict.
  • Do not support scripting to add custom build commands.

Read full review

Hung Vu | TrustRadius Reviewer
Hung Vu
View all 9 answers on this topic

Gradle

  • Still under development, not as mature as Maven
  • Build files aren't as easy to follow because they are so loose
  • The community isn't as large as Maven

Read full review

David Tanner | TrustRadius Reviewer
David Tanner
View all 8 answers on this topic

Performance

Apache Maven

Apache Maven 9.0
Based on 1 answer
Excellent tool to build a project, simple and easy to study, install and implement.

Read full review

Hung Vu | TrustRadius Reviewer
Hung Vu
View all 1 answers on this topic

Gradle

Gradle 3.0
Based on 1 answer
I have tried to use Gradle for projects several times in the past, but there is just so much work in maintaining the build file that it quickly becomes untenable. I have been using Maven for many years, and even though the build file can be complex, it works without maintenance between releases.

Read full review

David Tanner | TrustRadius Reviewer
David Tanner
View all 1 answers on this topic

Support

Apache Maven

Apache Maven 3.0
Based on 1 answer
Most of the support I've gotten is from coworkers. I'm sure there's a community out there who would know more, but I'm not aware of it.

Read full review

Anonymous | TrustRadius Reviewer
Verified User
View all 1 answers on this topic

Gradle

Gradle 8.7
Based on 3 answers
Gradle has been an excellent tool for Android development. It has helped us create multiple versions of the app for different environments. It also takes care of all the packaging needs in the background without having to write all the code related to that. It is a no brainer to use Gradle with Android applications.

Read full review

Mohit Goenka | TrustRadius Reviewer
Mohit Goenka
View all 3 answers on this topic

Alternatives Considered

Apache Maven

Ant, Maven's opposing framework, is often a point of comparison. Although Ant does not require formal conventions, it is procedural in the sense that you must tell Ant exactly what to do and when. It also lacks a lifecycle, along with goal definition and dependencies. Maven, on the other hand, requires less work as it knows exactly where your source code is as long as the pom.xml file is generated.

Read full review

Anonymous | TrustRadius Reviewer
Verified User
View all 9 answers on this topic

Gradle

SBT works fine for Scala but when I tried to use it with Java it was hard to configure and I gave up. Maven is awesome but the pom.xml file tends to be really big which makes it hard to read. Grunt is suitable only for js projects.

Read full review

Anonymous | TrustRadius Reviewer
Verified User
View all 8 answers on this topic

Return on Investment

Apache Maven

  • The tool has greatly improved our overall software build times and had a positive impact on our release schedules.
  • Being a free application from an Open Source Community, there was no upfront investment needed on our part.

Read full review

heather collins | TrustRadius Reviewer
heather collins
View all 9 answers on this topic

Gradle

  • In a distributed development environment, once we established a strong CI/CD model, Gradle proved to be a great choice to automate the various processes. Gradle also provides much flexibility, which is essential in today's development environment. The important benefit is that the CI/CD engineers can support development's needs quickly and reliably. This in turn supports faster testing and deployment, which generates higher ROI.

Read full review

Dirce Richards | TrustRadius Reviewer
Dirce Richards
View all 8 answers on this topic

Pricing Details

Apache Maven

General

Free Trial
—
Free/Freemium Version
—
Premium Consulting/Integration Services
—
Entry-level set up fee?
No

Gradle

General

Free Trial
—
Free/Freemium Version
—
Premium Consulting/Integration Services
—
Entry-level set up fee?
No

Add comparison