@bamboo Is that planned to push plugin authors to use extensions to configure default task settings, instead of configure them directly, I’m talking about some kind “best practices” guide. Also, would be nice to see this approach in Gradle Core plugins Because with Groovy it looks identically, but with Kotlin DSL task configuration still looks awkwardly to be honest, and even if dsl will be improved, you should know task class to configure it.

We are considering providing accessors for tasks known after plugin application but indeed that will still leave out some tasks.

Any suggestions on how to make build authors life easier in that regard is very much welcome.