[
https://issues.apache.org/jira/browse/LOG4J2-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238299#comment-17238299
]
Jeff Gullett commented on LOG4J2-2461:
--------------------------------------
At this point (over 2 years after my initial report), I expect that both
Eclipse and Javadoc fully support multi-release JAR files. Your link (which is
dead for me, perhaps I need to login to Oracle first?) indicates Javadoc was at
least updated. I have not confirmed such support was added to Eclipse, but it
would surprise me if it wasn't. I still question whether there is any reason
to NOT add the automatic-module-name to the manifest file. This is a
single-line change in the manifest file, and all sources that I have found
makes me think it would work as expected (e.g., only be used by software that
doesn't support mutli-release JAR files).
> 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)
