[
https://issues.apache.org/jira/browse/MJAVADOC-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753197#comment-16753197
]
Gili commented on MJAVADOC-569:
-------------------------------
Actually, I'm not sure that this issue is fully resolved.
"--add-modules" works for a simple "exports" but will fail for "exports
SecretPackage to MyFriend".
I tried using "--add-reads SecretPackage=MyFriend" but it seems that the
Javadoc tool is mapping the automatic module to the unnamed module as opposed
to the name specified by "Automatic-Module-Name". It doesn't make sense to
export "SecretPackage" to the entire world (the unnamed module) because it is
meant for private consumption. Any ideas?
> javadoc:aggregate fails with 'error: package org.w3c.dom is not visible' when
> mixing Java modules and non-modules
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MJAVADOC-569
> URL: https://issues.apache.org/jira/browse/MJAVADOC-569
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Environment: maven-javadoc-plugin 3.1.0-SNAPSHOT
> Java 12-ea+28
> Reporter: Gili
> Assignee: Robert Scholte
> Priority: Blocker
> Attachments: testcase.zip
>
>
> # Unpack testcase
> # Run {{mvn clean package javadoc:aggregate -e}}
> # {{javadoc:aggregate}} will fail with various errors like "(package
> org.w3c.dom is declared in module java.xml, but module module2 does not read
> it)"
> Note that module 2 isn't really a Java Module but we are treating it as such
> for the purposes of aggregating Javadoc across modularized and
> non-modularized code. Module 2 has no way of declaring its intention of
> reading the aforementioned package because it does not have a
> {{module-info.java}} file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
