You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2020/11/24 17:37:00 UTC

[jira] [Commented] (LOG4J2-2461) Add Automatic-Module-Name to the Manifest

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

Ralph Goers commented on LOG4J2-2461:
-------------------------------------

The fix I mentioned above was back-ported to Java 11.0.5 in [https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8222124.] I am wondering if this issue matters any more.

> Add Automatic-Module-Name to the Manifest
> -----------------------------------------
>
>                 Key: LOG4J2-2461
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2461
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 2.11.1
>            Reporter: Jeff Gullett
>            Priority: Minor
>             Fix For: 2.14.1
>
>
> Some tools (Eclipse, Javadoc) don't cleanly support multi-release JAR files.  These tools report an error when trying to reference the log4j-api module using the name org.apache.logging.log4j.  Adding this module name to the JAR manifest allows these tools to operate on the JAR despite not correctly locating the module-info.java file.



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