I ran a java survey recently where I asked developers on tools/frameworks they used in the last 12 months.

Respondants had the option to select multiple options from a predefined list of choices or select Others and provide their own choice. In this post we’ll be covering the responses of around 120 developers on the topic of build tools.

Build tools – Survey Results


  • Apache Maven – build automation tool used primarily for Java projects
  • Hudson – a continuous integration (CI) tool written in Java
  • Jenkins – an open source continuous integration tool written in Java. The project was forked from Hudson after a dispute with Oracle.
  • Gradle – an open source build automation system that builds upon the concepts of Apache Ant and Apache Maven and introduces a Groovy-based domain-specific language (DSL) instead of the XML form used by Apache Maven of declaring the project configuration
  • Apache Ant – a software tool for automating software build processes, which originated from the Apache Tomcat project in early 2000
  • SBT– an open source build tool for Scala and Java projects, similar to Java’s Maven or Ant.
  • Atlassian Bamboo – is a continuous integration and delivery tool that ties automated builds, tests and releases together in a single workflow
  • TeamCity – a Java-based build management and continuous integration server from JetBrains
  • Grape – a JAR dependency manager embedded into Groovy
  • Ivy – a sub-project of the Apache Ant project, a transitive dependency manager
  • Leiningen – a build automation and dependency management tool for the simple configuration of software projects written in the Clojure programming language

If you haven’t seen the previous posts on the survey results yet, here’s the list of topics already covered:

  1. Languages
  2. Web Frameworks
  3. Application Servers
  4. Data Access Tools for SQL
  5. SQL Databases
  6. Big Data
  7. Build Tools
  8. Cloud Provider