<!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: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">https://bugs.openjdk.org/browse/JDK-8322865</a></p>
<p><br>
</p>
</body>
</html>