Build automation for those who like XML
January 21, 2020

Build automation for those who like XML

Anonymous | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with Apache Maven

Maven is used across the org to build JVM based applications as well as few non-JVM ones which utilize the exec and release plugins to adhere to semantic version requirements. It is mainly used to solve build dependencies between internal and external applications.
  • Build resolution.
  • Sometimes useful error messages.
  • Lots of static XML.
  • Copypasta.
  • Allows for a hierarchical design via parent POMs, makes it great to define shared, overwritable properties.
  • BOM definitions allow for easy imports that are known to work together.
Maven was chosen out of convention as a static build tool. Personally, I prefer Gradle's less verbose syntax and modularity. Same with Bazel and Sbt.
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.

Do you think Apache Maven delivers good value for the price?

Yes

Are you happy with Apache Maven's feature set?

Yes

Did Apache Maven live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Apache Maven go as expected?

Yes

Would you buy Apache Maven again?

Yes

Builds JVM applications very well. Wouldn't recommend for other types of applications. Many useful plugins make sure applications build and run correctly, at the expense of overly verbose XML.