You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Varga (JIRA)" <ji...@apache.org> on 2019/03/26 18:29:00 UTC

[jira] [Created] (MJAVADOC-591) javadoc fails with maven.compiler.release=8 and Automatic-Module-Name

Robert Varga created MJAVADOC-591:
-------------------------------------

             Summary: 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


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 or defining source=8 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)