maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Karg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MJAVADOC-575) <source>8</source> fails when module-info.java exists
Date Thu, 07 Feb 2019 06:17:00 GMT

    [ https://issues.apache.org/jira/browse/MJAVADOC-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762402#comment-16762402
] 

Markus Karg commented on MJAVADOC-575:
--------------------------------------

I assume this is caused by Maven Javadoc Plugin adding --module-path as soon as it finds a
module-info.java file in the src folder. This should be modified in a way that the existence
of that file is to be ignored by the plugin as soon as the provided <source> is 8 or
older, because the aim of such a feature / files combination simply is to have JavaDocs created
"as if" the used JDK "would be" 8 - and JDK 8's JavaDoc tool simply ignores that file.

> <source>8</source> fails when module-info.java exists
> -----------------------------------------------------
>
>                 Key: MJAVADOC-575
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-575
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 3.0.1
>            Reporter: Markus Karg
>            Priority: Major
>
> Some projects are written for Java 8 but include a module-info.java class cross-compiled
using JDK 9. On JDK 11.0.2 the Maven Javadoc Plugin does fail with the following message:
>  error: option --module-path not allowed with target 1.8
> In fact, it is wrong that the Javadoc plugin uses the "--module-path" option once <source>8</source>
is provided.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message