From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

If I apply the plugin only in the root build, and not in any of the included builds, it all works fine.

So what I have is:
`rootbuild` includes `included-build` includes (in pluginManagement) `convention`

Sounds to me like a regression you should report.

Using a settings plugin to share repository configuration is fine as long as you don't need settings plugins from this plugin repository you are adding in your convention plugin.

Btw. you should consider adding a namespace to your convention plugins, either by naming them accordingly or by having a `package ...` statement in them. Plugin IDs without dot should usually stay reserved to built-in plugins to not risk a name clash in the future.

Thanks for the confirmation, I'm just preparing a repo for the reproducer.

Regarding names: we usually do that, yes, after we learned the hard way that having two slightly different `base-java-project` conventions in the same build does not work so well, when temporarily `includeBuild`ing yet another build that follows a similar pattern :sweat_smile:

<https://github.com/gradle/gradle/issues/24341>