Alternatives to Apache Maven logo

Alternatives to Apache Maven

Jira, Jenkins, Apache Maven, Gradle, and CMake are the most popular alternatives and competitors to Apache Maven.
1.5K
874
+ 1
370

What is Apache Maven and what are its top alternatives?

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.
Apache Maven is a tool in the Java Build Tools category of a tech stack.
Apache Maven is an open source tool with 1.9K GitHub stars and 1.5K GitHub forks. Here’s a link to Apache Maven's open source repository on GitHub

Apache Maven alternatives & related posts

Jira logo

Jira

12.5K
8.6K
1.1K
12.5K
8.6K
+ 1
1.1K
The #1 software development tool used by agile teams to plan, track, and release great software.
Jira logo
Jira
VS
Apache Maven logo
Apache Maven

related Jira posts

David Ritsema
David Ritsema
Frontend Architect at Herman Miller · | 10 upvotes · 51.5K views
atHerman MillerHerman Miller
Jira
Jira
Confluence
Confluence
GitHub
GitHub

We knew how we wanted to build our Design System, now it was time to choose the tools to get us there. The essence of Scrum is a small team of people. The team is highly flexible and adaptive. Perfect, so we'll work in 2 week sprints where each sprint can be a mix of new R&D stories, a presentation of decisions made, and showcasing key development milestones.

We are also able to run content stories in parallel, focusing development efforts around key areas of the site that our authors need first. Our stories would exist in a Jira backlog, documentation would be hosted in Confluence , and GitHub would host our codebase. If developers identify technical improvements during the sprint, they can be added as GitHub issues and transferred to Jira if we decide to represent them as stories for the Backlog. For Sprint Retrospectives, @groupmap proved to be a great way to include our remote members of the dev team.

This worked well for our team and allowed us to be flexible in what we wanted to build and how we wanted to build it. As we further defined our Backlog and estimated each story, we could accurately measure the team's capacity (velocity) and confidently estimate a launch date.

See more
Priit Kaasik
Priit Kaasik
Engineering Lead at Katana MRP · | 9 upvotes · 75.3K views
atKatana MRPKatana MRP
Slack
Slack
Jira
Jira
Intercom
Intercom
Confluence
Confluence
Bitbucket
Bitbucket
appear.in
appear.in
Papertrail
Papertrail
#RemoteTeam
#Agile
#CustomerSupportChat
#Notes
#SourceCode
#Logging
#Release
#InProductCommunication
#ContinuousDelivery
#Alerts
#Documentation
#Requirements

As a new company we could early adopt and bet on #RemoteTeam setup without cultural baggage derailing us. Our building blocks for developing remote working culture are:

  • Hiring people who are self sufficient, self-disciplined and excel at video and written communication to work remotely
  • Set up periodic ceremonies ( #DailyStandup, #Grooming, Release calls and chats etc) to keep the company rhythm / heartbeat going across remote cells
  • Regularly train your leaders to take into account remote working aspects of organizing f2f calls, events, meetups, parties etc. when communicating and organizing workflows
  • And last, but not least - select the right tools to support effective communication and collaboration:
  1. All feeds and conversations come together in Slack
  2. #Agile workflows in Jira
  3. InProductCommunication and #CustomerSupportChat in Intercom
  4. #Notes, #Documentation and #Requirements in Confluence
  5. #SourceCode and ContinuousDelivery in Bitbucket
  6. Persistent video streams between locations, demos, meetings run on appear.in
  7. #Logging and Alerts in Papertrail
See more

related Jenkins posts

Thierry Schellenbach
Thierry Schellenbach
CEO at Stream · | 23 upvotes · 47.6K views
atStreamStream
Go
Go
Travis CI
Travis CI
GitHub
GitHub
Jenkins
Jenkins
#ContinuousIntegration
#CodeCollaborationVersionControl

Releasing new versions of our services is done by Travis CI. Travis first runs our test suite. Once it passes, it publishes a new release binary to GitHub.

Common tasks such as installing dependencies for the Go project, or building a binary are automated using plain old Makefiles. (We know, crazy old school, right?) Our binaries are compressed using UPX.

Travis has come a long way over the past years. I used to prefer Jenkins in some cases since it was easier to debug broken builds. With the addition of the aptly named “debug build” button, Travis is now the clear winner. It’s easy to use and free for open source, with no need to maintain anything.

#ContinuousIntegration #CodeCollaborationVersionControl

See more
Tymoteusz Paul
Tymoteusz Paul
Devops guy at X20X Development LTD · | 15 upvotes · 354.7K views
Vagrant
Vagrant
VirtualBox
VirtualBox
Ansible
Ansible
Elasticsearch
Elasticsearch
Kibana
Kibana
Logstash
Logstash
TeamCity
TeamCity
Jenkins
Jenkins
Slack
Slack
Apache Maven
Apache Maven
Vault
Vault
Git
Git
Docker
Docker
CircleCI
CircleCI
LXC
LXC
Amazon EC2
Amazon EC2

Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

See more

related Apache Maven posts

Ganesa Vijayakumar
Ganesa Vijayakumar
Full Stack Coder | Module Lead · | 15 upvotes · 484.2K views
Codacy
Codacy
SonarQube
SonarQube
React
React
React Router
React Router
React Native
React Native
JavaScript
JavaScript
jQuery
jQuery
jQuery UI
jQuery UI
jQuery Mobile
jQuery Mobile
Bootstrap
Bootstrap
Java
Java
Node.js
Node.js
MySQL
MySQL
Hibernate
Hibernate
Heroku
Heroku
Amazon S3
Amazon S3
Amazon RDS
Amazon RDS
Solr
Solr
Elasticsearch
Elasticsearch
Amazon Route 53
Amazon Route 53
Microsoft Azure
Microsoft Azure
Amazon EC2 Container Service
Amazon EC2 Container Service
Apache Maven
Apache Maven
Git
Git
Docker
Docker

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more
Tymoteusz Paul
Tymoteusz Paul
Devops guy at X20X Development LTD · | 15 upvotes · 354.7K views
Vagrant
Vagrant
VirtualBox
VirtualBox
Ansible
Ansible
Elasticsearch
Elasticsearch
Kibana
Kibana
Logstash
Logstash
TeamCity
TeamCity
Jenkins
Jenkins
Slack
Slack
Apache Maven
Apache Maven
Vault
Vault
Git
Git
Docker
Docker
CircleCI
CircleCI
LXC
LXC
Amazon EC2
Amazon EC2

Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

See more
Gradle logo

Gradle

3.2K
2.2K
243
3.2K
2.2K
+ 1
243
A powerful build system for the JVM
Gradle logo
Gradle
VS
Apache Maven logo
Apache Maven

related Gradle posts

frido
frido
Apache Maven
Apache Maven
Gradle
Gradle

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.

See more
Java
Java
JavaScript
JavaScript
Node.js
Node.js
nginx
nginx
Ubuntu
Ubuntu
MongoDB
MongoDB
Amazon EC2
Amazon EC2
Redis
Redis
Amazon S3
Amazon S3
AWS Lambda
AWS Lambda
RabbitMQ
RabbitMQ
Kafka
Kafka
MySQL
MySQL
Spring Boot
Spring Boot
Dropwizard
Dropwizard
Google Analytics
Google Analytics
Elasticsearch
Elasticsearch
Amazon Route 53
Amazon Route 53
GitHub
GitHub
Docker
Docker
Webpack
Webpack
CircleCI
CircleCI
Jenkins
Jenkins
Travis CI
Travis CI
Gradle
Gradle
Apache Maven
Apache Maven
Jira
Jira
notion.so
notion.so
Trello
Trello
Vue.js
Vue.js
Flutter
Flutter
Application & Data

Java JavaScript Node.js nginx Ubuntu MongoDB Amazon EC2 Redis Amazon S3 AWS Lambda RabbitMQ Kafka MySQL Spring Boot Dropwizard Vue.js Flutter

Utilities

Google Analytics Elasticsearch Amazon Route 53

DevOps

GitHub Docker Webpack CircleCI Jenkins Travis CI Gradle Apache Maven

Cooperation Tools

Jira notion.so Trello

See more
CMake logo

CMake

292
28
0
292
28
+ 1
0
An open-source system that manages the build process
    Be the first to leave a pro
    CMake logo
    CMake
    VS
    Apache Maven logo
    Apache Maven
    Sonatype Nexus logo

    Sonatype Nexus

    231
    100
    0
    231
    100
    + 1
    0
    organize, store, and distribute software components
      Be the first to leave a pro
      Sonatype Nexus logo
      Sonatype Nexus
      VS
      Apache Maven logo
      Apache Maven

      related Sonatype Nexus posts

      Joshua Dean Küpper
      Joshua Dean Küpper
      CEO at Scrayos UG (haftungsbeschränkt) · | 4 upvotes · 10.7K views
      atScrayos UG (haftungsbeschränkt)Scrayos UG (haftungsbeschränkt)
      Sonatype Nexus
      Sonatype Nexus
      GitLab
      GitLab

      We use Sonatype Nexus to store our closed-source java libraries to simplify our deployment and dependency-management. While there are many alternatives, most of them are expensive ( GitLab Enterprise ), monilithic ( @Artifactory ) or only offer SaaS-licences. We preferred the on-premise approach of Nexus and therefore decided to use it.

      We exclusively use the Maven-capabilities and are glad that the modular design of Nexus allows us to run it very lightweight.

      See more
      Gonçalo Faustino
      Gonçalo Faustino
      Docker
      Docker
      OpenShift
      OpenShift
      SonarQube
      SonarQube
      Sonatype Nexus
      Sonatype Nexus
      GitLab
      GitLab
      Vault
      Vault
      Apache Maven
      Apache Maven
      AngularJS
      AngularJS
      Spring Boot
      Spring Boot
      #DeploymentWorkflow

      We use Docker for our #DeploymentWorkflow along with OpenShift SonarQube Sonatype Nexus GitLab Vault Apache Maven AngularJS Spring-Boot

      See more
      Apache Ant logo

      Apache Ant

      122
      82
      7
      122
      82
      + 1
      7
      Java based build tool
      Apache Ant logo
      Apache Ant
      VS
      Apache Maven logo
      Apache Maven
      JFrog Artifactory logo

      JFrog Artifactory

      87
      33
      0
      87
      33
      + 1
      0
      Enterprise Universal Repository Manager
        Be the first to leave a pro
        JFrog Artifactory logo
        JFrog Artifactory
        VS
        Apache Maven logo
        Apache Maven
        SBT logo

        SBT

        73
        25
        0
        73
        25
        + 1
        0
        An open source build tool for Scala and Java projects
          Be the first to leave a pro
          SBT logo
          SBT
          VS
          Apache Maven logo
          Apache Maven
          JitPack logo

          JitPack

          27
          22
          6
          27
          22
          + 1
          6
          JitPack builds GitHub Gradle and Maven projects on demand and provides ready-to-use packages
          JitPack logo
          JitPack
          VS
          Apache Maven logo
          Apache Maven
          Buck logo

          Buck

          16
          37
          3
          16
          37
          + 1
          3
          A build system developed and used by Facebook
          Buck logo
          Buck
          VS
          Apache Maven logo
          Apache Maven
          Pants logo

          Pants

          14
          26
          30
          14
          26
          + 1
          30
          Build system by Twitter, Foursquare, and Square
          Pants logo
          Pants
          VS
          Apache Maven logo
          Apache Maven
          Please logo

          Please

          8
          4
          0
          8
          4
          + 1
          0
          A Cross-Language Build System
            Be the first to leave a pro
            Please logo
            Please
            VS
            Apache Maven logo
            Apache Maven
            EventBus logo

            EventBus

            5
            3
            0
            5
            3
            + 1
            0
            An open-source library for Android and Java
              Be the first to leave a pro
              EventBus logo
              EventBus
              VS
              Apache Maven logo
              Apache Maven