Skip to content

chore: migrate to Kotlin Dokka 2.0#964

Merged
loosebazooka merged 1 commit intosigstore:mainfrom
vlsi:dokka2
May 16, 2025
Merged

chore: migrate to Kotlin Dokka 2.0#964
loosebazooka merged 1 commit intosigstore:mainfrom
vlsi:dokka2

Conversation

@vlsi
Copy link
Collaborator

@vlsi vlsi commented May 16, 2025

Summary

Dokka 2 is still experimental, however, we use very basic apis, so let's migrate and silence the warning.

Release Note

NONE

Documentation

NONE

Signed-off-by: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>
@vlsi
Copy link
Collaborator Author

vlsi commented May 16, 2025

By the way, I've no idea if we should keep publishing the documentation in "javadoc" format rather than html.

dokkaHtml feels better for Kotlin-based projects. For instance, dokka html format would probably describe extension functions better than javadoc.

At the same time, I've absolutely no clue which tools use -javadoc.jar artifacts from Central :)

@loosebazooka
Copy link
Member

I guess we don't publish the plugin to central so it doesn't matter? I'll just merge this for now to remove warning and we can revisit later.

@loosebazooka loosebazooka merged commit 6da9650 into sigstore:main May 16, 2025
12 of 13 checks passed
@vlsi
Copy link
Collaborator Author

vlsi commented May 16, 2025

I guess we don't publish the plugin to central so it doesn't matter?

It doesn't hurt publishing it.
I typically publish my Gradle plugins to both Central and Gradle's Plugin Portal for redundancy.

However, let's migrate to html later if needed. ChatGPT suggests one should use "javadoc" when publishing dokka-generated artifacts to Central :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments