Apache Maven vs Sonatype Nexus: What are the differences?
Developers describe Apache Maven as "Apache build manager for Java projects". Maven allows a project to build using its project object model (POM) and a set of plugins that are shared by all projects using Maven, providing a uniform build system. Once you familiarize yourself with how one Maven project builds you automatically know how all Maven projects build saving you immense amounts of time when trying to navigate many projects. On the other hand, Sonatype Nexus is detailed as "The world's best way to organize, store, and distribute software components". Deliver better, safer software even faster with software supply chain automation.
Apache Maven and Sonatype Nexus belong to "Java Build Tools" category of the tech stack.
Apache Maven and Sonatype Nexus are both open source tools. It seems that Apache Maven with 1.74K GitHub stars and 1.28K forks on GitHub has more adoption than Sonatype Nexus with 527 GitHub stars and 236 GitHub forks.
According to the StackShare community, Apache Maven has a broader approval, being mentioned in 305 company stacks & 142 developers stacks; compared to Sonatype Nexus, which is listed in 49 company stacks and 16 developer stacks.
What is Apache Maven?
What is Sonatype Nexus?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Sonatype Nexus?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Sonatype Nexus?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
We use Apache Maven because it is a standard. Gradle is very good alternative, but Gradle doesn't provide any advantage for our project. Gradle is slower (without running daemon), need more resources and a learning curve is quite big. Our project can not use a great flexibility of Gradle. On the other hand, Maven is well-know tool integrated in many IDEs, Dockers and so on.
Java build tool for internal processes: Jezebel daemon (in-mem classifiers/recommendations/feature analysis), Connemara (batch resume stream processor) and opes (opening elasticsearch plugin, simple process that listens for new incoming resumes and triggers analysis by Jezebel via a tcp json command).
All Java-Projects are compiled using Maven. We prefer it over Ant and Gradle as it combines lightweightness with feature-richness and offers basically all we can imagine from a software project-management tool and more.
Package management and build automation for the back-end, plus integration of front-end build automation using Gulp/Bower/NPM.
Necessary for Google j2objc