Skip to main content
TrustRadius
Apache Maven

Apache Maven

Overview

What is Apache Maven?

Apache Maven is an open source build automation tool.

Read more
Recent Reviews

TrustRadius Insights

Apache Maven is highly regarded by organizations and developers for its versatile use cases in building and packaging applications. For …
Continue reading

Apache Maven

9 out of 10
December 28, 2017
Incentivized
Apache Maven is used as a build tool in our organization. Maven along with Gradle are the 2 most used tools for building Java or Scala …
Continue reading

Apache Maven Review

5 out of 10
June 17, 2016
Incentivized
Maven is often used in our Tech Dev department in a variety of Java projects to help speed up the process of dependency configurations and …
Continue reading
Read all reviews

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Apache Maven?

Apache Maven is an open source build automation tool.

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

22 people also want pricing

Alternatives Pricing

What is Liquibase?

Liquibase is a database change management tool that helps teams release software faster and safer by bringing the database change process into existing CI/CD automation. According to the 2021 Accelerate State of DevOps Report, elite performers are 3.4 times more likely to incorporate database…

What is Bitrise?

Bitrise, software from the company of the same name in Budapest, helps users automate daily app development tasks from building through testing to deployment. With Bitrise, users can configure these tasks with a visual Workflow editor, with over 330 service integrations ready to roll. All…

Return to navigation

Product Details

What is Apache Maven?

Apache Maven Video

What is Apache Maven?

Apache Maven Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

Apache Maven is an open source build automation tool.

Reviewers rate Support Rating highest, with a score of 5.1.

The most common users of Apache Maven are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(60)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Apache Maven is highly regarded by organizations and developers for its versatile use cases in building and packaging applications. For instance, ARM marketing firm relies on Apache Maven as an integral part of their build infrastructure, simplifying the build process and facilitating dependency management for their Java-based web applications. This allows them to easily manage projects and utilize different project versions.

Similarly, Cognex, an enterprise organization, also utilizes Maven extensively across their entire code suite. By using Maven, they can streamline the management of third-party dependencies and customize build steps, making it easier to maintain and update their projects. Maven's integration with Git and Jenkins CICD pipeline further enhances efficiency by automating the build process.

Furthermore, Apache Maven finds extensive use in universities, serving as the main packaging tool for building and packaging applications within the development environment. Its adoption contributes to a standardized build process that spans multiple departments, ensuring uniformity and efficiency across various projects.

Another noteworthy application of Maven is in Java Enterprise products where it serves as a reliable system for dependency management. Companies rely on Maven to handle both standard Java Maven projects as well as Gradle-based projects, allowing for seamless collaboration between internal and external applications.

Moreover, open source community members frequently turn to Apache Maven for building their diverse range of open source projects. Its compatibility with any Java IDE provides users with support for code reuse and resource management.

Lastly, in organizations like Cognex's Tech Dev department, Maven shines in speeding up dependency configurations and project packaging for Java projects. It is often integrated with automation test projects and seamlessly works alongside Jenkins for continuous integration.

Overall, Apache Maven's versatile nature makes it an indispensable tool across industries and organizations of varying sizes, addressing crucial aspects like build automation, dependency management, documentation, and standardization of processes.

Simple Hierarchical Structure: Apache Maven offers a straightforward hierarchical structure for building and packing software artifacts, which has been positively mentioned by many users. This feature simplifies project organization and management effectively.

Different Configurations for Development and Production: Users have appreciated the ability of Apache Maven to support separate configurations for development and live production environments. This feature enables easy testing of applications and ensures reliable consistency throughout different stages of the project.

Easy Dependency Management: Multiple reviewers have highlighted the ease of adding and resolving dependencies in Apache Maven. This feature simplifies the process of managing external libraries and ensures that all required dependencies are included in the project.

Dependency Management Issues: Some users have experienced frequent conflicts during local project builds with Maven's dependency management system. These conflicts can make it challenging to resolve and manage dependencies effectively.

Manual Configuration of JAR Files: Users found it problematic and time-consuming to manually add and configure JAR files in Maven. This manual process can be error-prone, especially when dealing with complex projects with multiple dependencies.

Error Handling and Reporting Mechanism: Several users have expressed the need for improved error handling and reporting in Maven. They feel that the current mechanism lacks clarity and does not provide sufficient information for troubleshooting issues during build processes.

Users have made several recommendations regarding Apache Maven.

First, users recommend using Maven for automating Java projects due to its safety, reliability, and network compatibility. Additionally, Maven is considered easy to use for beginners and has extensive community support.

Second, users suggest referring to the documentation for better understanding and fully utilizing Maven's capabilities. They also recommend thorough training on Maven implementation to take advantage of its power as an automation tool for Java/Scala projects.

Third, users advise exploring other build tools like Gradle and considering specific project needs. They suggest researching and reading books or tutorials to become well acquainted with Maven. Additionally, leveraging the open-source community and considering alternative options before making a decision are also mentioned as valuable steps.

Overall, users find Apache Maven to be a reliable and popular build automation tool for Java projects. They recommend it for its safety, ease of use for beginners, documentation, and strong community support.

Attribute Ratings

Reviews

(1-14 of 14)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • Makes the build process simple and easy to do.
  • It provides a standard build system that can be adopted by multiple, different groups within an organization.
  • It's extensible with easy to use custom extensions which our developers take full advantage of.
  • The documentation could be a bit more detailed.
  • Initial setup for us in our environment was a bit of challenge.
  • The learning curve for this product is pretty steep. Your developers will definitely need some sort of training to get started and integrating it.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
  • Better project build and task automation than ant or any other conventional Java build configuration manager.
  • Easy dependency management for all popular java libraries, with the ability to support arbitrary dependency repositories (Nexus, e.g).
  • Better IDE integration. Still too many manual workflows in Eclipse and IntelliJ.
  • Similar to above, easier project-specific configuration management. I'm not aware of an ability to control which repositories are used by which projects, without updating the main maven config.
heather collins | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User
Incentivized
  • Apache Maven uses a simple hierarchical structure for building and packing a software artifact.
  • Different configurations of the software can be used while working on the dev server as opposed to a live production environment. This makes testing the application very easy.
  • One of the issues with building software using Apache Maven is that its cache resolution is not optimal. It pulls down all the artifacts onto the developer's local machine and can sometimes result in conflicts.
  • The build process can vary in time and gets progressively longer as the project's complexity increases.
Score 5 out of 10
Vetted Review
Verified User
Incentivized
  • Reuse code and resources
  • Compatible with a wide range of Java IDEs
  • It helps to download resources over the network.
  • Configuration is written into XML which is cumbersome.
  • New versions of libraries are added daily, It is very difficult for Maven to keep track of the dependancies.
  • It's inflexible and overcomplicated.
Score 7 out of 10
Vetted Review
Verified User
Incentivized
  • If you are building in the Java ecosystem, then Maven definitely has the biggest repository of artifacts needed for such projects.
  • It has a very simple to use extendable architecture. Everything is configurable through the Pom.xml file which is very simple to follow.
  • In our use of this software, we have found several issues with its dependency management system. Firstly due to its caching mechanism, it can sometimes show conflicts when building the project locally.
  • Adding and configuring the project to support manually added JAR files can be problematic. The error handling and reporting mechanism should be improved.
December 28, 2017

Apache Maven

Score 9 out of 10
Vetted Review
Verified User
Incentivized
  • 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.
  • Maven provides a very rigid model that makes customization tedious and sometimes impossible. While this can make it easier to understand any given Maven build, as long as you don’t have any special requirements, it also makes it unsuitable for many automation problems.
  • Maven has few, built-in dependency scopes, which forces awkward module architectures in common scenarios like using test fixtures or code generation. There is no separation between unit and integration tests
Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • It's easy to manage the libraries. Just need to update the pom file, you can easily manage and update libraries in one place.
  • Good to manage different modules.
  • Integrates with Jenkins. Compatible with other open source tools and continuous integration.
  • Sometimes it kept the old report, and caused the maven build [to] fail.
  • More improvements needed to manage different levels of pom.
June 17, 2016

Apache Maven Review

Score 5 out of 10
Vetted Review
Verified User
Incentivized
  • Facilitates build processes: through the use of POM files and plugins, this feature helps developers focus less on the tedious mechanical details of project implementation.
  • Well organized: users are able to locate their project information easily, whether it's dependencies, test reports, etc.
  • Catalyzes process for making updates and migrations: minimal time is needed for users to make changes to their project based on new installations, etc.
  • Compilation errors can be a bit extensive
  • Difficulty in maintaining jars in repository for large projects
  • Certain Maven conventions are set in stone, causing inflexibility (one artifact per project, etc.)
Return to navigation