hello everyone, I have a build using

buildSrc

which contains both an actual custom plugin and various convention plugins. I was unable to reference the custom plugin by id from the the convention plugins, so I tried moving the custom plugin to a directory of its own and use an

includeBuild

. However it appears that doing so disables parallel execution for the dependency resolution step of all the projects in the build. this is probably what

Because of the reliance on dependency substitution, composite builds may force configurations to be resolved earlier, when composing the task execution graph. This can have a negative impact on overall build performance, because these configurations are not resolved in parallel.

warns about but I don't understand why it behaves like this in this specific case. The only alternative I could find is to imperatively

apply()

the plugin, is that the recommended practice ?