Gradle Convention plugins vs apply from project root dir

Question

what are the reasons to use gradle convention plugin instead of using common gradle file apply from project root dir? is it faster or slower?

I can't find any reason to use the convention plugin except for a link to plugins instead of specifying the path to settings.

Answer 1

In the long run, cross-project configuration usually grows in complexity and becomes a burden. Cross-project configuration can also introduce configuration-time coupling between projects, which can prevent optimizations like configuration-on-demand from working properly.

For more details, please refer to this document.