Apache Maven Reviews and Ratings

Use Cases and Deployment Scope

We use Maven in our build pipeline to download and include correct versions of third-party dependencies in our application. The ability to keep track of indirect dependencies greatly simplifies the management of third-party libraries, which our application depends on. Maven is also used to apply custom build steps when building our application.

Likelihood to Recommend

Maven is great if you have an application with a lot of third-party dependencies and don’t want each developer to keep track of where the dependency can be downloaded. It’s also a great way to make it easy for a new developer to be able to build the application. It’s less suitable for simple projects without any third-party dependencies.

Use Cases and Deployment Scope

We use Maven for our build artifacts. It is a part of the pipeline for getting our code built and running in production. This works as an important cog in the delivery of new functionality and code to production. It is reliable and one of the parts of our build infrastructure that we don't have to be concerned about.

Likelihood to Recommend

Getting products built in an internal environment and out to the production environment. This is our most commonly used scenario. This might not be as useful as a solution if you are looking to architect a solution that requires lots of vendor support. This is a simple tool to use if you are willing to architect it yourself.

Use Cases and Deployment Scope

As a build tool, we are using Maven with our Java-based project to add the libraries and dependencies in the project. With the help of that, we need not explicitly download the various jar and put it into our project. This makes our project easy and manageable and also use a version of the project build using Maven.

Likelihood to Recommend

A project that we want to manage via libraries. Import and export various libraries and classes from one project to another. Add and download the project dependencies. Project structure or folder hierarchy. Various goals and parameters for different types of builds. Everything gets handled using a simple POM.xml file.

Use Cases and Deployment Scope

Apache Maven is used as a build automation tool and it simplifies the projects build process, dependency, and documentation. Apache Maven is able to solve many problems as below:

1. Software versioning.

2. Dependency management like includes the jars and other dependencies.

3. It has been integrated with the git and Jenkins CICD pipeline for the automatic build.

Likelihood to Recommend

We are using the java langauge to develop our application hence Apache Maven is one of the best suitable build tools available. Our use case has been Project and dependency management. Building the jar files Software versioning. Useful in maintaining consistency in the project.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

Apache Maven is well suited for an environment where you want an easy to use system that can be rolled out to multiple departments throughout the enterprise. Apache Maven is a good solution for those looking for a build process that can be customized as much as they require. This system will allow a consistent build process, but still be flexible enough for individual departments to customize a solution to meet their specific needs.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

If you're building a Java Enterprise application, you should use Maven. I'm not actually sure what the alternative is. Manually downloading Jar's and adding them to your classpath? Putting them in your source control repo? Hand-rolling everything you need, including String manipulation functions? This is really the only modern solution to Java library dependency management, and whether you use pom.xml, or build.gradle or some other abstraction, this is the de-facto standard for Java dependency management.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

In software development one of the major headaches for companies is managing third party libraries and dependencies. Apache Maven makes it a breeze on that front. We can lock in the specific versions of the libraries that we are currently using and can upgrade them at our own convenience.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

For small projects, Maven can identify unused and transitive dependencies. For large projects, as it contains a large number of XML files which makes it difficult to understand and maintain. Maven makes your project build on a network connection. Not enough documentation on the web for beginners. Debugging is not easy as it is difficult to find bugs in your code.

Use Cases and Deployment Scope

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.

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.