You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ross Goldberg (Jira)" <ji...@apache.org> on 2019/10/17 16:51:00 UTC

[jira] [Commented] (LOG4J2-2393) log4j-api-2.11.0.jar multi-release jar doesn't work in javadoc module-path

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

Ross Goldberg commented on LOG4J2-2393:
---------------------------------------

[~thosch] FYI, it looks like this was fixed in Java 11.0.5.

> log4j-api-2.11.0.jar multi-release jar doesn't work in javadoc module-path
> --------------------------------------------------------------------------
>
>                 Key: LOG4J2-2393
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2393
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.11.0
>         Environment: Java 10.0.2+13
> macOS 10.13.6
>            Reporter: Ross Goldberg
>            Priority: Minor
>
> I'm trying to javadoc code that contains a {{module-info.java}} that {{requires org.apache.logging.log4j;}}.
> I've included the jar from Maven Central that matches the coordinates {{org.apache.logging.log4j:log4j-api:2.11.0}} (which is a multi-release jar) on the module path.
> {{javac}} compiles the code fine, but the following simplified {{javadoc}} command outputs an error:
> {{javadoc --module-path ./log4j-api-2.11.0.jar -d ~/Desktop ./src/main/java/module-info.java}}
> Error:
> {quote}error: module not found: org.apache.logging.log4j
> 	requires org.apache.logging.log4j;{quote}
> When I manually repackaged {{log4j-api-2.11.0.jar}} as a non-multi-release jar, the {{javadoc}} worked (the simplified command above outputs an error about {{No public or protected classes found to document}}, but my real command works, and that error shows that the simplified command has progressed past the {{module not found}} error).
> Is there something wrong with {{log4j-api-2.11.0.jar}} that can be fixed while still maintaining it as a multi-release jar?
> Or does javadoc (from Oracle JDK 10.0.2) not support multi-release jars on the module-path?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)