Filter Ratings and Reviews
Filter 50 vetted Apache Maven reviews and ratings
Reviews (1-11 of 11)
Companies can't remove reviews or game the system. Here's why.
November 09, 2020
Apache Maven is being used throughout the entire enterprise organization. It's our go-to system to perform builds for our applications. Apache Maven makes it easy for us to have a uniform build system for multiple different departments. It standardizes the build process to ensure the quality of our build process. This allows the developers to focus on the actual code, not the build process itself.
- 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.
February 25, 2020
It is being used across the whole organization as the dependency management solution for all Java Enterprise products. It is used in both standard Java maven projects (using pom.xml) and gradle-based projects. We use a mix of publicly-available dependency downloads (such as mvnrepository.com), as well as local nexus servers. One downside in such a mixed-repo environment would be switching between profiles (in local settings) between projects. Some projects involve a local nexus server of "approved" libraries, whereas others allow any publicly-available repo. Switching between the two can involve IDE restarts and other minor annoyances in developer workflow.
- 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.
January 21, 2020
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.
May 02, 2019
We use Maven as the primary build tool for all of our Java projects. It allows us to manage all project dependencies, their versions, repository source, build, and deployment stage, It is easy to use and flexible, we just need to define our main dependency and it will pull out all necessary libraries and help to resolve conflict. With Maven, it is easy to manage our source code in a repository tool such as BitBucket and store all libraries in our Repository which we can share between all projects, so we do not need to replicate libraries in all source code repositories. Maven has a rich plugin which provides a various goal for the specific purpose based on project need such as report, log, version.
- Easy to install with GUI or command line, well integrated with almost IDE.
- Centralized locaiton for project configuration lifecycle managment.
- Has a rich plugin which supports various goals.
- Separate between source code and dependency in the project.
- Flexible on the configurations repository, built a parameter, goal so we could have a different solution for the different environment or stages such as dev, test or production.
- Good open source community and documentation.
- 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.
January 22, 2018
At ARM marketing firm when we started working on our in-house custom-built applications and delivering web solutions to our clients, we decided to go with Java based web applications since our developers had the most experience in that domain. Apache Maven is an Open Source tool from the Apache Software Foundation that we use for building and packaging our applications.
- 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.
Apache Mave is used by the whole organization to build an entire code suite (not at Cognex).
- Good build structure and open source community
- Excellent management of build artifacts (GAV)
- Integrates well with other tools
- Better support channels
January 16, 2018
At our university, we decided to purchase a new portal implementation to serve as the landing page for our students, faculty and staff members. We decided to go with a Liferay portal for that purpose. For building and packaging our applications we decided to use Open Source software Apache Maven. Maven is used throughout our development environment as the main packaging tool.
- 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.
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 applications.
- 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
It is very easy to understand. Being popular in the open source community, various open source projects can be built using Maven. We use Maven for developing in-house projects. All Java IDEs provide support for Maven and it's compatible with any Java IDE. Using Maven, one can reuse code and resources.
- 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.
March 17, 2017
I set up a set of automation test projects with Apache Maven. It managed several testing projects with different levels. I also integrated it with Jenkins. It helps with continuous integration.
- 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.
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 project packaging.
- 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.)
Apache Maven Scorecard Summary
What is Apache Maven?
Apache Maven is an open source build automation tool.
Categories: Continuous Delivery, Build Automation
Apache Maven Video
What is Apache Maven?
Apache Maven Technical Details
| Operating Systems: | Unspecified |
|---|---|
| Mobile Application: | No |
Frequently Asked Questions
What is Apache Maven?
Apache Maven is an open source build automation tool.
What are Apache Maven's top competitors?
GNU Make, Azure DevOps Services (formerly VSTS), and Red Hat Ansible Automation Platform are common alternatives for Apache Maven.
What is Apache Maven's best feature?
Reviewers rate Support Rating highest, with a score of 5.9.
Who uses Apache Maven?
The most common users of Apache Maven are from Enterprises and the Computer Software industry.