[
https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747230#comment-16747230
]
Gili commented on MJAVADOC-555:
-------------------------------
Please help me understand what should be possible to run as of today (currently
MJAVADOC-562 is marked as fixed and MJAVADOC-566 is not).
Should I be able to run {{javadoc:aggregate}} under JDK 12 linking to the JDK
12 online Javadoc? Alternatively, should I be able to run {{javadoc:aggregate}}
under JDK 12 linking to the JDK 11 online Javadoc? I don't mind either
approach. As it stands, I can't figure out how to mix named and unnamed modules
(with an {{Automatic-Module-Name}} entry).
> 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
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 3.1.0
>
> 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)
