This message was deleted.

Any

allprojects { ... }

and

subprojects { ... }

block introduces project coupling and should be avoided where possible. The simple truth is, that you shouldn't do it. Whenever you inject configuration from outside, you maybe introduce coupling and for sure make the build logic intransparent. The most idiomatic way is, that you have a convention plugin that all projects apply or that all other convention plugins apply and apply your plugin there.

Is that generally true even for the root project? The config-on-demand docs state:

. Coupling of the root project to subprojects does not impact configuration on-demand, but using the allprojects and subprojects in any subproject's build.gradle file will have an impact.

It definitely introduces coupling. It might not be a problem if the root project is always configued and configured first. But even if it would work, it still makes the build less transparent.

Cool. Thanks for the input!