Has anyone migrated to dokka 2 and use multi modul...

# dokka

[ansman]

Has anyone migrated to dokka 2 and use multi module HTML paired with the versioning plugin? I'm just getting that the root ask is skipped because it's not enabled

[mbonnin]

We do: https://github.com/apollographql/apollo-kotlin/blob/e5c9bf8727dbc2b1e479fcfe49f5e4237e872c51/build-logic/src/main/kotlin/Publishing.kt#L102

[mbonnin]

We publish kdoc in a separate module though, not the root one

[ansman]

Cool, I'll check it out!

[ansman]

Woah, you download the docs?

[mbonnin]

Yea so that I don't need a state locally. Maven Central is the state

[mbonnin]

Might not be 100% CC compatible though... Can't remember if it was

[hfhbd]

Downloading the docs is a very nice idea to also get a versioned package list url 🤔

[ansman]

Smart

[CLOVIS]

Oh @mbonnin, that's smart! I made a feature request to upstream this: https://github.com/Kotlin/dokka/issues/3977

[kevin.cianfarini]

I started looking into including version support for some of my libraries today and I cowered away from setting something up where I maintain each of the different versions from CI 😬

[kevin.cianfarini]

I also noticed that the kotlinx-coroutines library doesn't use the version plugin

[Jeff Lockhart]

I migrated my project that uses versioning to Dokka v2: https://github.com/jeffdgr8/kotbase/pull/32

(The docs themselves are under docs/api. In retrospect, I shouldn't have regenerated them in the same PR.)

[CLOVIS]

ah so you're committing all versions of the docs in the repository? I am not doing that

[Jeff Lockhart]

Not all published artifact versions, but every major or minor version. The API doesn't really change between patch versions. The docs directory contains both the documentation site markdown and API docs to publish to GitHub pages. I could probably change it so the API docs are only on the gh-pages branch. My deploy_api_docs.sh script currently just copies the docs to that branch rather than generating directly to it, which has made it easier to debug the generated docs before publishing them, and work around bugs like this one. But now that's being fixed in code, so I could probably safely skip that step now.