Actually attach Javadocs jar files to build #2988
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Followup to #2971.
maven-release-publisher.ymlchange was suspicious because Gradle should be able to determine that it's a dependency. This indicated that perhapsandroidJavadocsJarwas not a dependency after all.Testing strategy: similar to #2971 but with dry build being done off of this branch instead of after merging to main, thanks @sdhuka!
Followups -- looks like Amplify isn't releasing Javadocs either despite adding Dokka. Also adding Javadocs HTML to docs website, and fixing errors/warnings as mentioned in #2971.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.