[
https://issues.apache.org/jira/browse/MJAVADOC-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337402#comment-17337402
]
Robert Scholte commented on MJAVADOC-676:
-----------------------------------------
bq. Even worse, this library depends on things that are not able to run on the
module path.
I tend to close this as won't fix. If this project isn't "java module" ready,
it shouldn't provide an automatic module name.
The main condition (and maybe only reason) to provide an automatic module name
is when the project itself is java-module ready, but at least one dependency is
an automatic module (either via the manifest or filename).
It would probably be better if javac had already discovered this, but it can't
because the maven-jar-plugin provides the automatic-module-name.
> Can't generate javadoc when project has an automatic module name
> ----------------------------------------------------------------
>
> Key: MJAVADOC-676
> URL: https://issues.apache.org/jira/browse/MJAVADOC-676
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 3.2.0
> Reporter: Michael Simons
> Assignee: Robert Scholte
> Priority: Major
> Attachments: issues-master.zip
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
