[
https://issues.apache.org/jira/browse/LOG4J2-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238374#comment-17238374
]
Ralph Goers commented on LOG4J2-2461:
-------------------------------------
When the module-info file is present the jar is treated as a full Java module.
All the directives are honored. When the name is in the manifest JPMS treats it
as an automatic module named with the name specified in the manifest. But there
are no directives so the jar can access everything in the unnamed space and
everything can access it. See [Stephen's
article|https://blog.joda.org/2017/05/java-se-9-jpms-automatic-modules.html]
for more info.
All of this could have been avoided if it was module-info.json instead of
module-info.java.
> 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)
