Javadocs are missing for all okhttp 5.x

[aleksejb-marketpay]

On maven central all 4.x.x versions have empty javadocs jar with size of 261 bytes.
For example, version 4.0.0 https://repo1.maven.org/maven2/com/squareup/okhttp3/okhttp/4.0.0/okhttp-4.0.0-javadoc.jar (261 bytes)
Same for 4.7.2 https://repo1.maven.org/maven2/com/squareup/okhttp3/okhttp/4.7.2/okhttp-4.7.2-javadoc.jar
And latest ATM 4.11.0 https://repo1.maven.org/maven2/com/squareup/okhttp3/okhttp/4.11.0/okhttp-4.11.0-javadoc.jar
Versions 5.x.x looks ok, but they are in alpha ATM https://repo1.maven.org/maven2/com/squareup/okhttp3/okhttp/5.0.0-alpha.9/okhttp-5.0.0-alpha.9-javadoc.jar.
So all 4.x.x branch is missing javadocs.

[JakeWharton]

Maven Central is immutable so there's not really anything that can be done here.

[aleksejb-marketpay]

That is understandable, but can you fix it and release a new "patch" version with javadocs included? So we could just update dependency to something like 4.11.1?

[yschimke]

Now on 5.0, but I suspect it's still not working.

[looly]

On maven central 5.2.1 is empty Jar , look at this: https://repo1.maven.org/maven2/com/squareup/okhttp3/okhttp/5.2.1/

and from 5.0.0-alpha.15 to 5.2.1 has same problem.

5.0.0-alpha.14 is OK:

https://repo1.maven.org/maven2/com/squareup/okhttp3/okhttp/5.0.0-alpha.14/

[JakeWharton]

That is unrelated. The JVM artifact is now at okhttp-jvm and your build system should resolve it automatically.

[looly]

@JakeWharton OK，Thank you for answer questions， and use okhttp-jvm resolve it.

[fbricon]

For the 5.x stream, okhttp-jvm/5.0.0-alpha.11 was the last version with a Javadoc jar containing anything.

Since then, including 5.3.2, all javadoc jars only contain a barebone Manifest file.

Looks like this was caused by that "temporary" fix #8025