RFR: 8212233: javadoc fails on jdk12 with "The code being documented uses modules but the packages defined in $URL are in the unnamed module."

Aleksey Shipilev shade at redhat.com
Mon Feb 18 18:04:36 UTC 2019


On 2/18/19 6:51 PM, Martin Buchholz wrote:
> Over in https://mail.openjdk.java.net/pipermail/jdk-updates-dev/2019-February/000452.html you 
> volunteered to look at javadoc problems, and this bug is one of them, so perhaps you can add it 
> to your list?

Yeah, the test failure I mentioned at jdk-updates-dev@ is the leftover from applying your backport.
I did not manage to test it properly yet before suggesting for jdk11u backport.

> I expected this bug to be backported to Oracle jdk11, but there's no backport record in JIRA. I 
> don't know why my bug fix apparently does not resolve the serious maven-related problems seen in
> jdk11. My own backport seems to "work", but I don't whether an actual important bug is being 
> fixed.
There is no record for 11u in JIRA, because there is no backport to 11u. Replying in JIRA comment is
not enough, you need to follow this process: https://openjdk.java.net/projects/jdk-updates/ -- and,
given the patch does not apply cleanly to 11u, the additional RFR for 11u.

Time permitting, I'd give that backport a try again, if no one else gets to it first. I was also
hoping new maven-javadoc-plugin releases and fixes at least some of the issues.

-Aleksey

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://mail.openjdk.java.net/pipermail/javadoc-dev/attachments/20190218/f797b30d/signature-0001.asc>


More information about the javadoc-dev mailing list