Making the break: Moving from Maven to Gradle

If you've done a cursory look at Gradle, you might think “that would be nice, but we're stuck on Maven.” Well, you aren't, and you shouldn't be layering on the technical debt by staying with Maven. Moving from Maven to Gradle is quite reasonable; we'll cover the basic process, as well as some key pitfalls to avoid.

Maven is well known as a tool with some great core ideas, and an implementation that causes quite a few developers to froth at the mouth. Until recently, we all just had to grin and bear it … but now there's Gradle, which keeps the best ideas from Maven, discards the rest, and comes up with something that's fast, reliable, and scalable.

If you think you're wedded to Maven … you're not. Moving from Maven to Gradle isn't automatic, but it doesn't have to be painful, either. We'll cover the basic process, as well as the pitfalls and how to avoid them.

About Howard Lewis Ship

Howard Lewis Ship is the original creator of the Apache Tapestry project, and is a noted expert on Java framework design and developer productivity. He has over twenty years of full-time software development under his belt, with over fifteen years of Java. He cut his teeth writing customer support software for Stratus Computer, but eventually traded PL/1 for Objective-C and NeXTSTEP before settling into Java.

Howard has been developing financial and e-commerce applications in 100% Clojure since 2012.

Howard currently works for Wal-Mart's Global E-Commerce division. He lives in Portland, Oregon with his wife Suzanne, and his children, Jacob and Olivia.

More About Howard »