[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276152#comment-16276152 ]
Oleg Kalnichevski commented on LOG4J2-2133: ------------------------------------------- @[~ralph_go...@dslextreme.com] I think I have already shared my thoughts several months ago in one of the previous tickets about Android compatibility. I fully admit this might be a over-simplistic way of looking at things but I always imagined a logging abstraction to be a collection of interfaces and plain value objects plus a bootstrap mechanism for service providers. There appear to be many things, undoubtedly very useful, in Log4J API that should probably have put in core instead. 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)