From javadoc-dev:

For projects which contain only a module-info that transitively requires other modules - i.e. like java.se - the javadoc tool will fail.

This presents a problem for publishing those sorts of artifacts to Maven Central, which requires some javadoc jar in order to publish. The only workaround i've found is to go into the build tool, skip normal javadoc generation, and do it through a hacked script.

Is there a workaround I am missing, is this an intentional deficiency, or is this something that should be fixed?