[
https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279010#comment-16279010
]
Oleg Kalnichevski commented on LOG4J2-2133:
-------------------------------------------
@[~ralph_go...@dslextreme.com] Naturally, the idea is that Android users would
only need {{log4j-xxx}} (plus an Android specific provider) in order to get a
fully functional logging backend. {{log4j-api}} would contain JSE specific
code: {{StackLocator}} and {{ProcessIdUtil}} , JMX dependent code and so on and
depend on {{log4j-xxx}}. That _should_ provide 100% backward compatibility for
existing users while making Log4J logging abstraction more portable.
Oleg
> 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)
