Andy Pemberton Rotating Header Image

Maven vs. Ivy - by the numbers

I’ve had a few conversations lately about software tools and technologies — how to use them, how to pick them, how to know when to change, etc. These conversations can be exciting, educating, emotionally charged, productive, and sometimes not.

In a recent, very positive exchange, one colleague asked if I preferred Maven over Ant or Ant + Ivy simply because I had more experience on Maven.

Generally, I couldn’t say I preferred one technology stack over the other because I simply don’t know enough about the organization to make the call.

From a purely technical perspective though, my gut told me there is a brighter future in Maven than in Ant+Ivy. My reasons for this opinion are grounded in my experience, so I decided to research a few factors I consider important when it comes to technology tool selection.

Apache Maven Apache Ivy
Founded 2002
Latest Stable Release 1/20/2012 9/30/2010
Jenkins Plugin Installs ~50,000
Contributors 128
GitHub repositories 43,866

Couple of interesting observations from the stats above:

  • While Ivy is ‘2 years newer’, it’s last stable release was roughly 2 years earlier than Maven.
  • There are roughly 1500% more GitHub repositories referencing Maven than Ivy
  • There are roughly 1400% more contributors for Maven than Ivy (according to, anyway)

Google Trends also has an interesting view contrasting these two projects: Google Trends: Apache Maven, Apache Ivy

When discussing open source software projects, I usually think “we need to consider the vibrancy of the community”. How many people and organizations are contributing? How often? What other well known projects integrate with this tool?

From my view - when it comes to technology selection, it’s often OK to “follow the crowd”.

4 Comments on “Maven vs. Ivy - by the numbers”

  1. #1 Andy Pemberton
    on Dec 17th, 2012 at 12:37 pm

    Oh, by the way - here’s a really great article from Les Hazlewood on his perspective, having done a ton of Ant/Ivy and Maven work:

  2. #2 Brian
    on Dec 22nd, 2012 at 7:20 am

    The first thing I though of was to include gradle in the google trends report.

  3. #3 Frederic
    on Dec 22nd, 2012 at 8:36 am

    Hi Andy,

    I believe that both Maven and Apache Ivy are already being replaced in many projects by Gradle. Gradle is really the way forward to go in terms of build tools, plus writing a build script using code(groovy) rather than xml is such a massive advantage.

  4. #4 Andy Pemberton
    on Dec 22nd, 2012 at 1:08 pm

    @Brian, @Frederic - agreed, actually I made the same point. This particular conversation / organization is focused on Maven / Ivy, but Gradle may actually be a more progressive, forward thinking approach. I’m a huge Groovy (+ Grape) fan.

Leave a Comment