I'm a bit unsure how to achieve a multi-module build setup with the following structure: ```/build-l...

# dokka

[Emil Kantis]

I'm a bit unsure how to achieve a multi-module build setup with the following structure:

/build-logic/src/main/kotlin/dokka-conventions.gradle.kts
/build.gradle.kts                        (applies dokka-conventions)
/subproject-A/module-1/builds.gradle.kts (applies dokka-conventions + kotlin-jvm)
/subproject-A/module-2/builds.gradle.kts (applies dokka-conventions + kotlin-jvm)
/subproject-B/module-1/builds.gradle.kts (applies dokka-conventions + kotlin-jvm)
/subproject-B/module-2/builds.gradle.kts (applies dokka-conventions + kotlin-jvm)
/subproject-C/builds.gradle.kts          (applies dokka-conventions + kotlin-jvm)

my multi-module index page in /build/dokka/index.html only contains docs for subproject-A. Sometimes I manage to get it to output all modules, but it's incredibly flaky - not sure what causes the failure/success.. Perhaps worth mentioning: using Kotlin 1.8.10 and tried with both Gradle 7.6 and 8.0.

[Emil Kantis]

My dokka-conventions just adds an include for README.md for all DokkaPartial tasks

[Adam S]

Dokka currently doesn’t work very well with multimodule + parallel + build/config cache + project isolation. It might work better by disabling as much of the above as possible, but generally I’m not sure there’s a very good workaround.

But don’t worry! I’m on the case https://github.com/adamko-dev/dokkatoo/

[Emil Kantis]

It's not really an option for us to disable those things.. I guess we just end up not using dokka for the time being. 🙂

[Emil Kantis]

and I'll keep an eye on dokkatoo!