[
https://issues.apache.org/jira/browse/MJAVADOC-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337426#comment-17337426
]
Christian Stein commented on MJAVADOC-676:
------------------------------------------
{quote} ... this project isn't "java module" ready ...
{quote}
As far as I can see from the attached and linked project, the project is "java
module" ready. So, it would run happily on the module-path, promoting its name
via the manifest entry.
Only its deps are not "java module" ready, nor Java modules. So, why are they
all put on the module path?
> 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)
