Apache Maven

“half of the people don't even know what to do when maven fails inexplicably”

“I never have to worry about reading gradle/maven docs or anything like that”

“Maven solved the package distribution decades ago.”

“If you ever used Maven, NPM or... I can't think about any other tool that doesn't automatically check checksums and signatures.”

“has largely been replaced by maven, which is gradually being replaced gradle”

“No one in DotNet is waging an equivelent holy war about Gradle vs Maven etc...”

“managed to use maven repositories for 3 decades now with very few of these issues”

“Maven 4 will offer alternative file types via extensions!”

“Maven's been very nice in the decade and a half I've used it”

“Maven is plenty and any time I get back to a repo that has that instead of gradle or sbt I'm much happier.”

“the signing of JARs that are uploaded to the repository, and the fact that most release processes are not fully automated”

“Maven has deterministic dependency resolution (unless you use version ranges, but don't do that)”

“I dislike Gradle and use Maven, I don't want to program my build”

“it's focus on building in standard way is fantastic”

“It's perfect for small and medium sized projects, and for service-oriented architectures/microservices”

“It's perfect for code that is broken into medium-sized projects”

“The core plugins give you everything you need to build a self-contained jar”

“it's dependable, well documented, and it just plain works”

“with Maven it can easily happen that some edits don't "show" up in behavior”

“Maven config just tells IDE locations and dependencies.”

“I like a lot that Maven doesn't allow to code in the build config”

“Maven is XML (yuck) but is okay with the IDE integrations”

“Maven is old and cranky but if something else replaces it, it will probably be quite similar anyway”

“Pretty modern stack. I would start a government service using those today.”

“it's declarative and HARD to make non-trivial things”

“With Maven it is easy to add a plugin with harmful payload as dependency”

“you get a giant maven error stack trace which you now need to try and understand”

“both of which are complex and tiresome, requiring you to deal with either XML (Maven) or Groovy/Kotlin”

“Requires structured namespace ownership and signed artifacts, making identity more explicit at publish time”

“has been solved good enough by Apache Maven more than 2 decades ago”

“You can mount the current directory into docker and run an image of your tool.”

“at least it's been mostly the same since 2006”

“writing maven projects in Java with Eclipse. It works great.”

“Maven was a great idea. Introduce a high barrier to entry for publishing packages.”

“Maven is excellent! Once you understand it, you can work with almost any Maven project without needing to learn the specifics.”

“only Maven requires doing a clean install from time to time as it fails to properly track what needs updating”

“the quality of packages on offer in PIP and NPM versus Maven and NuGet”

“Java Maven artifacts typically name the exact version of their dependencies.”

“every time I have to do a thing in JVM dealing with maven feels like I need a goat or chicken”

“Its package system (Maven and the like) is ok, but not great.”