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 2019/08/10 17:35:00 UTC
[jira] [Commented] (LOG4J2-2672) Automatic-Module-Name missing from
some jars
[ https://issues.apache.org/jira/browse/LOG4J2-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16904482#comment-16904482 ]
Ralph Goers commented on LOG4J2-2672:
-------------------------------------
For some reason log4j-1.2-api had a packaging type as bundle so the jar plugin wasn't running. log4j-slf4j-impl overrides the default jar plugin configuration and isn't specifying the automatic module name.
> Automatic-Module-Name missing from some jars
> --------------------------------------------
>
> Key: LOG4J2-2672
> URL: https://issues.apache.org/jira/browse/LOG4J2-2672
> Project: Log4j 2
> Issue Type: Bug
> Components: log4j 1.2 emulation
> Affects Versions: 2.11.0
> Reporter: Stephen Colebourne
> Priority: Major
>
> log-4j-1.2-api v2.10.0 contained the line "Automatic-Module-Name: org.apache.log4j" in the MANIFEST.MF file. As far as I can tell, all subsequent releases do not contain the Automatic-Module-Name (despite the "runtime dependencies" documentation page).
> log4j-slf4j-impl also does not contain Automatic-Module-Name
> This may affect other jar files, I haven't checked all of them.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)