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.
Mostly it is very suitable for any product based company who wants to add a CI system for their products. This tool is perfectly suitable for a company which releases builds very frequently. By using this tool they can reduce a tremendous amount of manual effort. If company's budget is not high and if they can not afford the premium plan then this tool won't be suitable for them because the basic version of this tool won't provide much functionality
First thing is this tool is scalable which is the biggest advantage of this tool. It won't take much time in setup and making it ready. It has a very good user interface.
This tool has almost every source code repository support like Git, SVN, Microsoft Foundation Server etc. Moreover, it has very good support for various build tools like Visual Studio, MSBuild etc., which makes it even batter.
We can trigger multiple builds at a time with the Premier subscription.
It allows users to apply many deep levels of configurations which make the whole system even easier.
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.
Mostly I don't have much more recommendation for improvement because this tool provides almost everything which would be required in any continuous integration system. But still I would suggest improvement in the reporting system. The build report is a field where they can make improvement by adding more information if they want.
The overall usability of Apache Maven is very good to us. We were able to incorporate it into our company's build process pretty quickly. We deployed it to multiple teams throughout the entire enterprise. We got good feedback from our developers stating that Apache Maven has simplified their build process. It also allowed to to standardize the build process for the entire enterprise, thus ensure that each development team is using the same, consistent process to build code.
I can't speak to the support, as I've never had issues. Apache Maven "just works," and errors were user errors or local nexus errors. Apache Maven is a great build/dependency management tool. I give it a 9/10 because occasionally the error message don't immediately indicate a solution...but again, those errors were always user or configuration errors, and the Maven documentation is extensive, so I don't find fault in Maven, but in its users.
Ant is useful if your build is heavily based on customs scripts running in the right order. Maven greatly simplifies the process to keep track of and download build dependencies compared with Apache Ant. If your build is based on multiple custom scripts running in a specific order there is a lot of overhead in Maven compared to Apache Ant.
In my previous company I have used Jenkins for maintaining their CI system. Even this tool is also very good. The good thing about this tool is it’s an open source project. So in terms of pricing, we can consider this tool as an alternative to continua CI. One has to compare both of the products before going to use any one because both have their own benefits and drawbacks.
Basically, this tool will reduce manual effort of creating, deploying and testing software products. So ultimately it will reduce manpower which would otherwise be required for such things.
It is time saving and improves the overall performance of the entire team and system.
