Apache Maven vs Please: What are the differences?
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; Please: A Cross-Language Build System. Please is a cross-language build system with an emphasis on high performance, extensibility and reproduceability. It supports a number of popular languages and can automate nearly any aspect of your build process.
Apache Maven and Please can be categorized as "Java Build" tools.
Some of the features offered by Apache Maven are:
- 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)
On the other hand, Please provides the following key features:
- Build files
- Build targets
- Build labels
Apache Maven and Please 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 Please with 811 GitHub stars and 76 GitHub forks.
What is Apache Maven?
What is Please?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Please?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Please?
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