Javadocs not building properly

[AllanWang]

Build log

In some instances, it seems like the source jar or javadocs jar doesn't exist. If I were to build it locally, I will get the following files for the retrofit submodule in the lib folder:

-rwxrwxrwx 1 ... users 46477 Oct 28 23:23 data-1.0-SNAPSHOT.jar
-rwxrwxrwx 1 ... users 25511 Oct 28 23:23 data-1.0-SNAPSHOT-javadoc.jar
-rwxrwxrwx 1 ... users 16067 Oct 28 23:23 data-1.0-SNAPSHOT-sources.jar
-rw-r--r-- 1 ... users  5293 Jan 24 19:26 retrofit-1.0.0-sources.jar
-rwxrwxrwx 1 ... users  4244 Oct 29 00:14 retrofit.jar
-rwxrwxrwx 1 ... users 25511 Oct 29 00:14 retrofit-javadoc.jar
-rwxrwxrwx 1 ... users  1325 Oct 29 00:14 retrofit-sources.jar

However, the javadocs page is blank.

For cases like core, it does seem to generate something.

It also looks like for multi gradle module projects, linking the main javadocs page is blank, and you have to specify the submodules yourself in the url.

I've adapted our main build.gradle to generate the javadocs and sources like the jitpack example.

Our gradle and all the other bits can be found here

[AniketSK]

I also get the same issue. Javadocs are generated but not picked up by jitpack. Could we know where they're supposed to be or how they should be generated? Particularly when using gradle and dokka.

[viggy96]

I've found that I had to add a few extra lines to my build.gradle to get JitPack to pick up the Javadoc.

publishing {
  publications {
    mavenJava(MavenPublication) {
      from components.java
      afterEvaluate {
        artifact javadocJar
        artifact sourcesJar
      }
    }
  }
}

Turns out the "afterEvaluate" block is critical.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.

[viggy96]

Keeping this open.