how do I fix missing javadoc jar errors on maven central?

# multiplatform

[edwinRNDR]

how do I fix missing javadoc jar errors on maven central?

[Paul Weber]

I don’t remember exactly what I did, but this article helped me a whole lot with basically all questions regarding publishing a lib to maven central:
https://proandroiddev.com/publishing-android-libraries-to-mavencentral-in-2021-8ac9975c3e52

[edwinRNDR]

thanks but I feel my problem just falls outside of the scope of this article as it seems to be an mpp issue

[Robert Jaros]

Do you use dokka plugin?

[Robert Jaros]

I'm using this configuration in my project to publish javadoc jars:
https://github.com/rjaros/kvision/blob/master/build.gradle.kts#L57-L74

[edwinRNDR]

I do use dokka plugin. You can check my gradle configuration here: https://github.com/openrndr/openrndr/blob/master/build.gradle

[edwinRNDR]

It is a bit complex as it is a mix of mpp / jvm subprojects

[edwinRNDR]

can this be done without dokka? I have a lot of problems using dokka

[edwinRNDR]

(it is slow and occasionally runs out of memory)

[Robert Jaros]

As far as I know maven central only checks the existence of the javadoc jar, not its content. So you could probably just create empty jars for your artifacts and publish them.

[edwinRNDR]

yeah that's what I am at now 🙂 I am wondering though, how much does that cripple user experience?

[edwinRNDR]

seeing that I haven't had working javadoc jars for my local publications.. not much?

[edwinRNDR]

Thanks for your pointers @Robert Jaros they have helped me a lot

[ephemient]

this will create a javadoc jar:

val javadocJar by tasks.registering(Jar::class) {
    from(tasks.dokkaJavadoc)
    archiveClassifier.set("javadoc")
}
...
artifact(javadocJar)

simpler than Robert's solution, because Gradle already knows how to handle task outputs as files, and get a task from a task provider