Javadocs not being published
See original GitHub issueDescribe the bug
It appear the last published version of our javadocs under the new group id is 1.0.0-RC10
https://www.javadoc.io/doc/com.expediagroup/graphql-kotlin-schema-generator/1.0.0-RC10
RC11, 1.0.0, 1.1.0, and 1.2.0 all do not have published docs
Here are the changes published in RC11: https://github.com/ExpediaGroup/graphql-kotlin/releases/tag/1.0.0-RC11
Expected behavior Javadocs are published to Maven Central and therefore to javadoc.io
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Javadocs are not being published to Maven #651 - GitHub
Per https://repo1.maven.org/maven2/com/amplifyframework/core/1.1.0/, we are publishing sources, artifacts, Maven pom, and signatures.
Read more >JavaDoc will not publish on jenkins - Stack Overflow
It publishes javadocs as .jars for every sub-module. The javadocs are to be found in the sub-module directory not in the parent directory....
Read more >Javadoc archive doesn't get published to Maven - Old Forum
I am using the older 'maven' plugin because 'maven-publish' doesn't work with the release plugin (townsfolk) I create three archives.
Read more >Javadoc FAQ - Oracle
Where can I find the Javadoc tool and its documentation? ... How can I exclude or skip certain public members or classes from...
Read more >Generate JavaDocs that aren't completely worthless - Medium
Step 1: Figure out how to use the `javadoc` command, or better yet install the maven plugin: maven-javadoc-plugin from org.apache.maven.plugins.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
1.2.2 docs now published:
Reopening as unsure if lib upgrade actually fixed the issue or not - we need to verify it first.