Anyone generating and publishing javadoc for a multi-project build? How do you create links from one subproject to another? I've found https://github.com/SgtSilvio/gradle-javadoc-links which automatically sets up javadoc.io links, and (more importantly to me) resolves element-list and/or package-list from JARs to use with

-linkoffline

, which should cover the case for when a subproject depends on another (the javadoc.io link for that version doesn't exist yet as it's being generated before publishing) Do you know of other plugins? Do you have other approaches to handle that situation?

That's just the usual aggregation situation actually. Make an outgoing variant in the dependency project that publishes

javadoc.destinationDir

with a task dependency to

javadoc

. In the dependent project consume that variant and use that directory as second argument to

linksOffline

.

Do you happen to have a publicly available example of that kind of setup? (fwiw, and iiuc, the gradle-javadoc-links doesn't derive the element-list (from the library JAR), but resolves (extracts) it the javadoc JAR, and it defaults to linking to javadoc.io which uses the same source; so there's no additional external dependency at build time because the JARs come from the same servers as other dependencies, and there shouldn't be broken links as javadoc.io and the plugin use the same inputs)

Unfortunately, no