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

Gradle Community

Maybe, I guess I should have tried it. intelliJ says that map doesn't exist on subprojects though... I dislike groovy :rolling_on_the_floor_laughing::wink:

Ah, wait, you asked the other way around :smile:

Why should on want to switch to Groovy DSL :-D

I don't but I'm not going to migrate this existing project to kotlin right now

I copied my own kotiln code to add functionality that I use on a regular basis. I just don't know the quick way to migrate this

But well, of course the Kotlin version is doing task configuration avoidance while the Groovy version of it is not.

Groovy version with lazy would probably be something like
```tasks.named('dependencies') {
   dependsOn(subprojects*.tasks*.matching { it.name == 'dependencies' })
}```
or something like that.

Hm, no, that's not good either, it will also break task configuration avoidance and that for all tasks

Maybe
```tasks.named('dependencies') {
   dependsOn(subprojects.collect { "${it.path}:dependencies" })
}```

:point_up: that's what I would also do (using a string to "lazily" access the tasks in the subprojects).
You can drop the `.configure` if you like. It's also lazy without it: `tasks.named('dependencies') { ... }`

Ah, yeah, right. Was late, thanks. :smile: