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

Gradle Community

I am on mobile but what about getting the task collection and pass it to the depends on instead of nesting?

You could collect task names for all signing tasks if they have some kind of regular names (using `tasks.names.filter { .. }`) and then use `tasks.withType&lt;AbstractPublishToMaven&gt;().configureEach { dependsOn(signTaskList) }`

Another way is to register dummy task, have it depend on all signing tasks and make all publish to maven tasks depend on it

That is if I understood correctly what you do want in this case of course

```public inline fun &lt;reified T : Task&gt; TaskContainer.namedLazily(
    name: String,
    action: Action&lt;in T&gt;? = null,
): TaskCollection&lt;T&gt; {
    val collection: TaskCollection&lt;T&gt; = withType&lt;T&gt;().matching { it.name == name }
    if (action != null) collection.configureEach(action)
    return collection
}```

this should be lazy, but you shouldn't need the matching part because you want all tasks that withType returns 

<@U01DUV4Q882> how would I get all the publishing tasks?

<@U01DUV4Q882>, aren't tasks realized on calling `matching`? I surely hope not but am not sure about it.

val publishingTasks = tasks.withType&lt;Publish&gt;()

<@UJUMPU407> <https://melix.github.io/blog/2022/05/gradle-laziness.html|https://melix.github.io/blog/2022/05/gradle-laziness.html>

So far I have:

```val signingTasks = tasks.withType&lt;Sign&gt;()
tasks.withType&lt;AbstractPublishToMaven&gt;().configureEach {
  dependsOn(signingTasks)
}```
which at least doesn't have any errors with a dry run. Now to actually test it.

iirc all publish task registered by maven-publish plugin have regular names so you could match them using simple regex. They had names like `publish(PublicationName)To(RepositoryName)Repository`

Interested on your results, share here please :)

<@UJUMPU407> I originally had something like that where I iterated through the targets and built the task names from their publications but it was getting long and more complicated than I wanted

In my case for maven I am using nexus publish plugin so I have publishToSonatype task too

So matching is eager as I remember. But `tasks.withType&lt;T&gt;().matching { .. }` would only realize tasks of type `T` as expected.

Looks like

```val signingTasks = tasks.withType&lt;Sign&gt;()
tasks.withType&lt;AbstractPublishToMaven&gt;().configureEach {
  dependsOn(signingTasks)
}```
did the trick :smile:

Yes, that's the very first suggestion of Javi :-)

<@UJUMPU407> exactly. That's why you usually should prefer an `if` in the configuration block if you don't need the actual collection, but want to configure depending on name. :-)