[
https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276128#comment-16276128
]
Remko Popma commented on LOG4J2-2133:
-------------------------------------
Is it an option to make log4j-api an automatic module?
This can be done by adding an attribute to the manifest.
That’s what I did with picocli (see the [manifest
section|https://github.com/remkop/picocli/blob/31e8f99237cea492605f7a58011e0d9769066e74/build.gradle#L62]
in build.gradle) to keep it binary compatible with Java 5.
> Log4J 2 appears incompatible with Android platform due to inclusion of Java 9
> classes (class file version 53)
> -------------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-2133
> URL: https://issues.apache.org/jira/browse/LOG4J2-2133
> Project: Log4j 2
> Issue Type: Wish
> Components: API
> Affects Versions: 2.9.1, 2.10.0
> Reporter: Oleg Kalnichevski
> Attachments: Screenshot from 2017-11-28 09-41-37.png
>
>
> Log4J 2 appears incompatible with Android platform due to inclusion of Java 9
> classes (class file version 53). Please see screenshot attached.
> I fully admit that there might be a way to make Android ignore those files
> but it is still disheartening that Log4J 2 APIs have dependencies on things
> that go beyond providing a thin logging abstraction layer.
> Oleg
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
