[
https://issues.apache.org/jira/browse/MJAVADOC-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MJAVADOC-591.
-----------------------------------
Resolution: Fixed
Assignee: Robert Scholte
Fix Version/s: 3.1.1
Fixed in
[56979750c1752c811da28ff058aebc83b1fd018b|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commit;h=56979750c1752c811da28ff058aebc83b1fd018b]
Thanks for the patch!
> javadoc fails with maven.compiler.release=8 and Automatic-Module-Name
> ---------------------------------------------------------------------
>
> Key: MJAVADOC-591
> URL: https://issues.apache.org/jira/browse/MJAVADOC-591
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
> Affects Versions: 3.1.0
> Reporter: Robert Varga
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 3.1.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In a module, which defines an Automatic-Module-Name and (inherits)
> maven.compiler.release=8, but does not set source=8, javadoc generation fails
> with:
> {code:java}
> 16052 [ERROR] Exit code: 2 - error: option --module-path not allowed with
> target 8
> 16052 [ERROR] error: option --add-modules not allowed with target 8
> 16052 [ERROR] error: option --patch-module not allowed with target 8
> 16053 [ERROR]
> 16053 [ERROR] Command line was: /home/nite/jdk-12/bin/javadoc @options
> @packages
> {code}
> This occurs with both javadoc-11.0.2 and javadoc-12. Using either
> maven-javadoc-plugin-3.0.1, defining source=8 or removing
> Automatic-Module-Name works just fine.
> I think the problem is that maven.compiler.release is propagated to release
> property, but that is not taken into account when --add-modules is generated
> and propagated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
