This message was deleted.

Sure, you can just create a publication and configure your task as artifact for it. But iirc the cleaner way would be to define a custom component and publish that.

Sorry, I meant the other way around, I want to call

publications.create("")

based on the result of a task

How is that the other way around?

That sounds like it's modifying the task graph during execution, right?

Oh, ok

The use case is I want to create plugin marker publications based on an Annotation processor:

@GradlePlugin(
  id = "com.example",
  description = "cool stuff"
)
abstract class MyPlugin: Plugin<Project> {
  ...
}

Well, the precompiled script plugin plugins do something like this. But I guess they just look at the filenames present maybe.

Regarding plugins, you could also write your plugin with the precompiled „syntax“ and as a side effect, your plugin is registered automatically.

But better for the Kotlin ones. Iirc the Gradle one does bad action in

afterEvaluate

or something like that, making it hard to configure those publications then.

Oh I was too slow 😐

No you were not, I did not mean to write precompiled script plugins, which is an option too of course

But even with precompiled script plugins the gradle plugin block is still needed to set the display name and a description. But yes, the plugin „just“ iterates over the files.

I see. I think I'll keep the

gradlePlugins {}

for now. Sounds like it's not worth the extra hoops. Thanks anyways for the ideas!