<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 1/2/24 10:20 AM, Jonathan Gibbons
wrote:<br>
</div>
<blockquote type="cite" cite="mid:99ab0677-8708-4a0e-8f42-0d74b9799f13@oracle.com">
<p><br>
</p>
<div class="moz-cite-prefix">On 1/2/24 10:17 AM, Jonathan Gibbons
wrote:<br>
</div>
<blockquote type="cite" cite="mid:e914adac-577a-4c10-be6f-bf6238f005ac@oracle.com">
<p><br>
</p>
<div class="moz-cite-prefix">On 12/27/23 12:10 PM, Ethan McCue
wrote:<br>
</div>
<blockquote type="cite" cite="mid:CA+NR86i3nkpvazJRygZ2ANvdyXVoJf_gi=2xCst52s6vvZrKeQ@mail.gmail.com">
<div dir="ltr">For projects which contain only a module-info
that transitively requires other modules - i.e. like <a href="http://java.se" moz-do-not-send="true">java.se</a> -
the javadoc tool will fail.<br>
<br>
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.<br>
<br>
Is there a workaround I am missing, is this an intentional
deficiency, or is this something that should be fixed?</div>
</blockquote>
<p>Hi Ethan,</p>
<p>Thanks for the report. This is for sure not an intentional
deficiency!<br>
</p>
<p>This needs to be investigated and fixed as appropriate. <br>
</p>
<p>-- Jon<br>
</p>
</blockquote>
<p><br>
</p>
<p><a class="moz-txt-link-freetext" href="https://bugs.openjdk.org/browse/JDK-8322865" moz-do-not-send="true">https://bugs.openjdk.org/browse/JDK-8322865</a></p>
<p><br>
</p>
</blockquote>
<p><br>
</p>
<p>Ethan,</p>
<p>There is a partial/imperfect workaround.</p>
<p>When you list the source files explicitly, you get an
(inappropriate) error about no classes found to document. You can
workaround that issue by using a combination of setting the source
path (with either `--source-path` or `--module-source-path`) and
specifying the module (with --module). With that combination, you
can get past the "no classes found" message, and javadoc will
generate a full set of files, including the files for the module
in question .... but ... it appears there's a bug in the top-level
`index.html` page that is generated, and which should redirect to
the module page. Instead, it redirects to itself. That is in
itself a bug.</p>
<p>-- Jon<br>
</p>
</body>
</html>