[
https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732526#comment-16732526
]
Gili commented on MJAVADOC-555:
-------------------------------
Regarding #4, how would that work exactly? If you look at the testcase, you'll
notice that we're running the Javadoc tool against unpacked files. I don't see
how you would add a manifest file in this context.
I tried manually adding MANIFEST.MF containing *Automatic-Module-Name: module2*
but it did not make a difference.
Either MANIFEST.MF isn't being picked up by the Javadoc tool, or
*Automatic-Module-Name* is not sufficient in this case (i.e. we need
*module-info.java*).
> Javadoc:aggregate fails 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: 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)
