should I use `buildSrc` or convert all `.gradle` files to Kotlin dsl, preparing to refactor app to M...

# android-architecture

[Mohamed Ibrahim]

should I use buildSrc or convert all .gradle files to Kotlin dsl, preparing to refactor app to Modules?

[Joost Klitsie]

what do you wish to achieve?

[Mohamed Ibrahim]

preparing to refactor app to Modules?

[Vincent Williams]

Im not sure either of your suggestions relate to modules. You dont need kotlin dsl or buildSrc for multi-module

[Mohamed Ibrahim]

the idea is to organize dependencies and versions across all modules

[Joost Klitsie]

Okay so buildSrc is a place to put scripts which have access to the gradle API and can be referenced from build.gradle scripts.

[Joost Klitsie]

you can put in JVM languages, such as Java, Groovy or Kotlin in the buildSrc

[Joost Klitsie]

So if you have many different modules, using the buildSrc is a good way to go, as you can put that in the root project and then reference it from your modules' build.gradle files

[Joost Klitsie]

if you do not have a whole lot of modules, then I would advise to use Kotlin everywhere

[Joost Klitsie]

as I read here a topic by a guy that had 140 modules and noticed that script initialization is a bit slow for build.gradle.kts scipts (like 1s, but times 140 it is a lot)

[Joost Klitsie]

so you can use the kotlin-dsl plugin in the buildSrc to write kotlin files

[Joost Klitsie]

There is also people saying you shouldn't use buildSrc as it makes initial builds slower https://proandroiddev.com/stop-using-gradle-buildsrc-use-composite-builds-instead-3c38ac7a2ab3

[Joost Klitsie]

but in my experience the ease of buildSrc makes it a good choice

[Mohamed Ibrahim]

Thank you, I’ll go with buildSrc for now