[ https://issues.apache.org/jira/browse/MJAVADOC-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MJAVADOC-569. ----------------------------------- Resolution: Not A Problem Assignee: Robert Scholte {quote} error: package org.w3c.dom is not visible (package org.w3c.dom is declared in module java.xml, but module module2 does not read it) {quote} This is the real issue and can be solved by adding {{--add-modules java.xml}} (to the options file). The maven-javadoc-plugin cannot know that module is required too, so it is up to the developer to add this to the configuration of the plugin. He must do that with {code:xml} <additionalOptions> <option>--add-modules</option> <option>java.xml</option> </additionalOptions> {code} > 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)