[
https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16734537#comment-16734537
]
Gili commented on MJAVADOC-555:
-------------------------------
[~rfscholte] I see what you are doing:
* Using --patch-module to compile module2 as if it were a module
* Adding module2 to the list of sources
In theory, this should work for javadoc-cannot-link-to-automatic-modules.zip as
well but in practice it does not. Did you try running that testcase against
your latest code? It doesn't seem to be doing the above patching. I'm not sure
why.
> 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
>
>
> # 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)
