Also, another nube question - should I specify plugin in root gradle if I ever have to use it in modules?

Applying the plugin in the root project with apply false or true ensure using the same version in all modules

Ah, so it is not mandatory

No, you can even remove the root build gradle file and have subprojects if you have configured the repositories in the settings one

Any performance implication? Or I wonder why we all still have root gradle file

I think it is not only the version, but about the classpath too

It *might*y be necessary to have a plugin in the root project or in another way in a common classloader like as dependency in

buildSrc

or being present in the settings script classpath. Some plugins need to cooperate on application in different projects, for example using a shared build service. If you don't have the plugin in a common classloader, the classes are not the same and it does not work. But I would only do that if it is necessary, otherwise it is just visual clutter

Thank you people