Java Champion Hendrik Ebbers recently wrote an article about Maven and Gradle published by DZone. In his work he reflects the aspects where both Maven and Gradle succeed and fail. Plus, he considers static modules, an idea that would bring out and combine their best aspects.
A short abstract:
For several years, I’ve been really frustrated with the build tools for Java-based projects. In my work, I have seen several Java projects and modules that use different build systems. Thankfully, most projects I have seen over the last years are built on Maven or Gradle. Based on this trend, you only need to know two different systems to understand the basic structure and dependencies of a project. I don’t want to give an overview of all build systems that can currently be used to define the build of a Java based project — I think that they can all can be easily split into two different types:
Currently, Maven and Gradle are the best-known build systems, and each of them is related to one of those types. Let’s have a deeper look at both of them.
Hendrik Ebbers is Java Architect at Canoo Engineering AG and lives in Dortmund, Germany. His focus is UI technologies, Middleware and DevOps in addition to research and development. He is the founder and leader of the Java User Group Dortmund and gives talks at user groups and international conferences such as JavaOne, Devoxx, JFokus JAX and more. He blogs about UI related topics at www.guigarage.com. He is also a writter for the Java Magazine and a co-creator of JavaFX Ref Card for DZone.
Hendrik is one of the lead developers of DataFX that is used in several Java projects. This year Hendrik started the open source project Dolphin Platform. Here Hendrik is one of the lead developers and he is responsible for the JavaEE and Spring integration as well as the JavaFX client part.
Hendriks JavaFX book "Mastering JavaFX 8 Controls" was released 2014 by Oracle press. Hendrik is Java Champion, JavaOne Rockstar and JSR expert group member.