[ 
https://issues.apache.org/jira/browse/MJAVADOC-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753251#comment-16753251
 ] 
Gili commented on MJAVADOC-569:
-------------------------------

export-to-testcase.zip also exposes another bug.
 * Run "javadoc:aggregate".
 * In the module listing, select "module1"
 * Notice that no packages or classes are visible
 * Go back to the module listing and select "module2" (a module), "module2" (a 
package), "Module2" (a class)
 * Notice that method createModule1() returns "Module1" (a class). Click on 
that class.
 * Notice that "module1" (a module) really does contain packages and classes.

I'm not sure whether this is a bug in the Javadoc tool or the Maven plugin. If 
it is a bug in the Javadoc tool, I'm not sure how to generate a minimal 
testcase for them (without Maven). Do you generate a batch file in this case? 
Or maybe you are able to report it to them.

> 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)

Reply via email to