This message was deleted.

Besides that

allprojects { ... }

is bad per-se, you have the project there. The argument to that closure is the project.

whats wrong with allProjects?

It is bad practice, it introduces project coupling, ... You should use it, as well as

subprojects { ... }

Project coupling works against some more sophisticated features like parallel execution and so on.

hmm, I want to set those two flags on all android projects in the build, is there a more idiomatic way of doing it?

The idiomatic way is to not do cross-project configuration. Instead write a convention plugin and apply it where you want it's effect to be applied.

Well, yes, but there is no way to enforce people to use the conventions plugin, is there? Having possibility of varying java version in the build is way worse, no?

No, having unclear and harder to maintain build and additionally losing same of the more sophisticated features is way worse. If you want to programmatically enforce usage of some convention plugin, you could e.g. use some static code analyzer.

okay thank you