[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16734594#comment-16734594 ]
Robert Scholte commented on MJAVADOC-555: ----------------------------------------- Looking closer to the exception: https://google.github.io/guava/releases/27.0.1-jre/api/docs/ is indeed plain old javadoc, it doesn't contain modules as we want to generate here. I think this is a weird restriction, is there a reason why the external links should be module-based too? > 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: javadoc-cannot-link-to-automatic-modules.zip, > testcase.zip, toolchains.xml > > > # 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)