Likelihood to Recommend
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.
Employee in Information TechnologyHigher Education Company, 5001-10,000 employees
- 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.
Team Lead in EngineeringFinancial Services Company, 10,001+ employees
- 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.
Apache Maven 9.0
Based on 1 answer
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.
Engineer in Product ManagementTelecommunications Company, 10,001+ employees
Return on Investment
- 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.
Premium Consulting/Integration Services—
Entry-level set up fee?