Buck vs Apache Maven: What are the differences?
Buck: A build system developed and used by Facebook. Buck encourages the creation of small, reusable modules consisting of code and resources, and supports a variety of languages on many platforms; Apache Maven: 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.
Buck and Apache Maven can be primarily classified as "Java Build" tools.
Some of the features offered by Buck are:
- Speed up your Android builds. Buck builds independent artifacts in parallel to take advantage of multiple cores. Further, it reduces incremental build times by keeping track of unchanged modules so that the minimal set of modules is rebuilt.
- Introduce ad-hoc build steps for building artifacts that are not supported out-of-the-box using the standard Ant build scripts for Android.
- Keep the logic for generating build rules in the build system instead of requiring a separate system to generate build files.
On the other hand, Apache Maven provides the following key features:
- Simple project setup that follows best practices - get a new project or module started in seconds
- Consistent usage across all projects means no ramp up time for new developers coming onto a project
- Superior dependency management including automatic updating, dependency closures (also known as transitive dependencies)
Buck and Apache Maven are both open source tools. Buck with 6.81K GitHub stars and 1.02K forks on GitHub appears to be more popular than Apache Maven with 1.74K GitHub stars and 1.28K GitHub forks.
What is Buck?
What is Apache Maven?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
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