The dynamic Groovy DSL and the heterogeneous plugin APIs will make you google everything.Moreover, the whole team has to learn Gradle or you will be depending on the single Gradle ninja in your team. Gradle does an awesome job in speeding up your builds with features like incremental builds, daemons and clustered builds. You can do everything within the build script as you write them with the full-fledged programming language Groovy. Gradle is really powerful and flexible, but also complex, hard to learn and to cope if applied to real-world projects.

There is only the right tool for the right job. Both Maven and Gradle can be great or painful - depending on the project and team. Finally, you have to try out Gradle on your own and make up your own opinion. You can read many blogs about this “Maven or Gradle?” topic and everybody tells you another story. )Īnd at the end, it’s also a matter of taste. I won’t talk you into moving back to Maven. If you and your team are already familiar with Gradle and you are using it happily in practice for a while, you can definitely go on with Gradle. This post aims at developers who are currently using Maven and are wondering if they should use Gradle instead. It’s a story about enthusiasm and disillusionment. In this post, I like to tell you about my experiences with Gradle and why I finally migrated back to Maven. So I tried Gradle in two real-world projects. Sounds like something you don’t want to miss. It’s the future of building Java applications” they said. Disclaimer and Target Group of this Post.Java Ecosystem, Kotlin, Engineering Management, Sociology of Software Development Why I Moved Back from Gradle to Maven

Migrate maven to gradle android studio