With the version catalog, we don’t need this module to have an organized set of dependencies. This module has different Kotlin objects for the names of the dependencies, the Gradle plugins and all the version numbers. The most used technique nowadays in my experience is to use the Gradle Kotlin DSL to manage dependencies by creating a module, usually called buildSrc. Let’s see how to use it in a project, what are we going to gain using this tool, and what can be some of its disadvantages.

Now, we have a new tool to manage dependencies, called version catalog, and the great thing is that it can be used with Groovy and with the Kotlin DSL. Then, we jumped to the Kotlin Gradle DSL, and magically we could use the same language for our configuration files and for our base code. Easy to learn, not crazy different to Kotlin or Java, but it could be better. If you are an Android developer with experience, you have gone through the different phases of using Gradle to manage dependencies in Android.įirst, it was done through Groovy.

Latest gradle version android