Adam

Thanks for the log, I see `ValueClassSupportKt.isValue_safe` in there so I think this will be fixed soon by #890

Understood, this would be a breaking change. As a compromise, what about moving the files so they are visually organised, but retaining the package name so the code stays the...

Alternatively, use a more convention method of leaving the classes in the current package and marking them with `@Deprecated` and `@ReplaceWith`. Because the tasks are abstract classes, they could even...

> Alright, I haven't found strong evidence for using `by` in setting properties, it might due to my false memory. Are you thinking about how you can do `val someTask...

My pleasure! For reference the results of applying `kotlin-dsl` are specified here: https://docs.gradle.org/7.5.1/userguide/kotlin_dsl.html#sec:kotlin-dsl_plugin One of the changes that isn't explicitly stated is that the Kotlin language level will be changed...

I made some good progress but then I got stuck when I reached the integration test config, because it's a bit of a beast. https://github.com/Kotlin/dokka/blob/83174361becb2af227159834cdf6e14db9300c53/integration-tests/build.gradle.kts I think most of the...

@IgnatBeresnev I see you've added the 'Gradle Plugin' label, and while this PR would help with that, it's more about the improving the general Gradle build config of the entire...

With regards to labels, what about a 'build config' or 'ci/cd' label that would cover the build scripts, and also GitHub Actions, Qodana, TeamCity etc?

I've made some good progress! All shared build-config now comes from buildSrc convention plugins, not from `subprojects{}` or `allprojects{}` blocks. This makes the build much more modular, because it's not...

So I've submitted a few PRs and they make some progress towards improving the plugin, but actually started re-implementing the plugin mostly to get my head around it, but also...