OkHttp 4.0.1 publishes a javadoc jar, but the jar ...
# squarelibraries
d
OkHttp 4.0.1 publishes a javadoc jar, but the jar only holds a MANIFEST.MF file, no actual javadocs or KDocs. Is this intentional? Why? (https://repo1.maven.org/maven2/com/squareup/okhttp3/okhttp/4.0.1/)
j
When I switched us to MkDocs I broke the Javadoc jar. We can fix it I assumed nobody was using it.
d
Well I came across it as I was trying to figure out if/how javadoc jars are used in general. Supposedly IDEs use them, but I don’t know if that’s still true when a sources jar is also distributed. And depending on if/how javadoc jars are used, I was curious if the format of the HTML inside the javadoc jar is important, or if e.g. I could distribute KDocs HTML and name it artifact-javadoc.jar.