Where to add `dependencyGuard{}` closure in project with multi modules & flavors?

[trietbui85]

For example, there are 3 modules in my project: app, utils and feature.
In app, there are also 2 flavor: dev and prod.

So, where should I add the dependencyGuard{} closure? In project-level build.gradle, or in all module-level build.gradle, or only in app > build.gradle?

And moreover, should I update configuration("releaseRuntimeClasspath") to reflect the flavor? It means configuration("prodReleaseRuntimeClasspath") ?

[azabost]

So, where should I add the dependencyGuard{} closure? In project-level build.gradle, or in all module-level build.gradle, or only in app > build.gradle?

It depends on what exactly you want to focus on. You probably expect to have consistent dependency versions across all modules, so I think adding the configuration to the top-level (e.g., app or similar) module would suit your needs, because that's where all your dependencies converge (including transitives) to create the final artifact.

And moreover, should I update configuration("releaseRuntimeClasspath") to reflect the flavor? It means configuration("prodReleaseRuntimeClasspath") ?

Yes, absolutely. If you have custom build variants other than debug and release, you must take that into account, because every variant has its own classpath.