This message was deleted.

error message:

org.gradle.api.plugins.UnknownPluginException: Plugin [id: 'app.softwork.gradle.bug.publishedSettingsPlugin'] was not found in any of the following sources:

- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Included Builds (None of the included builds contain this plugin)
- Plugin Repositories (plugin dependency must include a version number for this source)

You probably need to

includeBuild("gradle-logic/plugin-testing")

in your root build settings script.

This works, but with this change, each build isn't independent anymore, is it?

Just that you include a build does not add it to any class path. That's why the settings plugin cannot be found. It either has to be in the class path of the id found in the plugin repositories or included builds. But probably not in builds included by included builds. If you would apply a plugin from

gradle-logic

and that would bring the

plugin-testing

plugin onto the class path as dependency, it would probably be found.

But if including a build does not add the deps to the settings classpath, how does the first sample work? https://github.com/hfhbd/testingGradle

Gradle sees that this build will build the plugin with the requested ID, so builds it and adds it to the class path.

Interessting, thanks! So adding it to the classpath is expected and a feature, not a bug. So final question, how does Gradle see it? And why does it don't work with another dependecy (but simillar project as https://github.com/hfhbd/testingGradle)?

How does it see what? And where does it not work?

I have a similar build like https://github.com/hfhbd/testingGradle but with other

published

dependency, containg a settings plugin too. I added the dependency to the real artifact notation in the build-logic build script, and want to use the settings plugin in the root settings file, like in the sample. But I always get the error, the settings plugin is not found:

- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Plugin Repositories (plugin dependency must include a version number for this source)

Interessting the line

Included Builds (None of the included builds contain this plugin)

is missing, so how does Gradle "see" which dependency/included build provides the plugin ids? Does Gradle parse the meta-inf/services of each jar?

It neither reads jars, nor module files for plugins by included builds, because they do not exist yet potentially. As I said, the included build is only built if actually needed. From your abstract description I cannot tell, as the abstract description could be imprecise. Show as MCVE what does not work

That's my problem, the minimal reproducer does work, the full project doesn't. I can't publish the full project, but I could send it to you via pm.

You cannot apply a plugin in

plugins { ... }

just by adding it to the class path. You could either apply it in a convention plugin in

build-logic

and apply that convention plugin in your root build, or you could apply it the legacy way using

apply(plugin = "app.softwork.kobol.versions")

outside the

plugins { ... }

block.

Thank you! Still curious why this works inside the plugins block here, but its okay :D https://github.com/hfhbd/testingGradle

Because there it comes directly from a build that is included in the plugin management block

Ah, because I (accidentally) added the

include(":published")

so it uses the local script and not the published one, stupid mistake. Thanks, finally understand why the reproducer works.