Ranked in these QuestionsQuestion Ranking
Pro Massive central repository
Maven's central repository is very large and extensive and holds almost every open source Java project out there.
Maven is very opinionated and declarative. This means that most developers will easily understand how your build system works. They don't have to guess which file will end up in the
jar. An IDE can also import any project and easily reason how everything is organized and fits.
Pro Built-in Dependency Resolution
It saves lot's of time, even more when you know how to use it properly.
Apache Maven is very popular in the Open Source community. With many open source projects using it as their build tool of choice. Considering that the Open Source community is rather large and usually helpful so there are a lot of guides and tutorials out there written by third-party sources on Maven.
Pro IDE Support
Almost all of the most used Java IDEs have special support for Maven built in out of the box or through plugins available to download.
Pro Lots of plugins
The fact that it's open source and that it's very popular means that Maven has hundreds of open source plugins available.
Maven uses XML syntax for it's configuration file, which is very verbose and tends to get complicated quickly.
Con Scripting missing extension by plugin only
Some build automation would easily be achievable with a tiny bit of scripting. Regrettably, maven forces everything to happen within XML or a plugin.
Con Difficult to customize
If you want to do everything The Maven Way, great. If you want or need to deviate from that, good luck.