[
https://issues.apache.org/jira/browse/MJAVADOC-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958207#comment-17958207
]
Olivier Lamy commented on MJAVADOC-823:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#1201|https://github.com/apache/maven-javadoc-plugin/issues/1201].
> legacyMode keeps using module-info.java (-sourcedirectory still use as well
> as java files input)
> ------------------------------------------------------------------------------------------------
>
> Key: MJAVADOC-823
> URL: https://issues.apache.org/jira/browse/MJAVADOC-823
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: javadoc
> Affects Versions: 3.11.1
> Reporter: Olivier Lamy
> Assignee: Olivier Lamy
> Priority: Major
> Fix For: 3.11.2
>
>
> When using legacyMode, javadoc should ignore all module-info.java when
> building javadoc.
> But the plugin is still using -sourcepath option with a list of directories
> AND a file as argument with all .java files. This means for project partially
> converted to java modules, aggregated javadoc may work as javadoc will still
> see some module-info..java because of scanning directories.
> In legacy mode, we can remove the use of -sourcepath parameter
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
