Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR
Fixes the publication errors:
Notes
I have set up Dokka to generate docs in the typical Kotlin template. I've decided to adopt the recently released alpha v2 config syntax, because v1 will eventually be deprecated.
For packaging the Dokka HTML output as an old-school javadoc jar I've made use of the popular Gradle Maven Publish Plugin by vanniktech, which is used by Ktor and OkHttp just two mention two popular ones.
How to test
Dokka
Execute
It will place the generated docs in
kotlin-sdk/build/dokka
. You can also double check that the(source)
links point to the right GitHub URLs.Local publication
If you have the code signing locally configured, you can execute
./gradlew publishToMavenLocal
. This will place the generated files under/home/bence/.m2/repository/dev/openfeature/
.(If you don't have code signing, comment out
signAllPublications()
inkotlin-sdk/build.gradle.kts
)For me it generated the following files, hopefully everything that is required by the Sonatype repository:
If you extract the javadoc jars, they should contain the html docs.