[ https://issues.apache.org/jira/browse/MJAVADOC-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757577#comment-16757577 ]
Robert Scholte commented on MJAVADOC-569: ----------------------------------------- I missed those questions, but here are my thoughts: - I don't understand why the export to the unnamed module is required. If both module1 and module2 are available on the modulepath I would expect them to see each other. So we need to finetune that. - The plugin has the info to calculate if the {{export to}} is relevant. But if module2 has a dependency on module1, then it makes sense to add it to the modulepath, otherwise (if it had a module descriptor) it wouldn;t even compile. > 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: export-to-testcase.zip, 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)