[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16734204#comment-16734204 ]
Gili commented on MJAVADOC-555: ------------------------------- {{javadoc:jar}} is similarly impacted. Reading [https://bugs.openjdk.java.net/browse/JDK-8212233] JDK12 and up will not support mixing named and unnamed modules. Maven plugins cannot use Java modules due to MPLUGIN-341. If I try invoke {{javadoc::jar}} on a Maven plugin (which is an unnamed module) that depends upon a named module, it fails with the aforementioned error. Hopefully the fix for {{javadoc:aggregate}} and {{javadoc:jar}} will be the same. > Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain > module-info.java > ------------------------------------------------------------------------------------------- > > Key: MJAVADOC-555 > URL: https://issues.apache.org/jira/browse/MJAVADOC-555 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: jar, javadoc > Affects Versions: 3.1.0 > Environment: Maven 3.6.0 > maven-javadoc-plugin 3.0.2-SNAPSHOT (required for Java 11 support) > Reporter: Gili > Priority: Major > Attachments: testcase.zip > > > # Unzip testcase > # Run {{mvn clean install javadoc:aggregate}} > # Build fails with: {{Exit code: 2 - javadoc: error - No source files for > package module2}} > Per MPLUGIN-341, Maven plugins cannot contain {{module.info.java}}. One of my > projects builds under Java 11 and is fully modularized except for one module > which is a Maven plugin. Due to the aforementioned issue, I cannot use > {{javadoc:aggregate.}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)