[
https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276133#comment-16276133
]
Ralph Goers edited comment on LOG4J2-2133 at 12/3/17 10:27 PM:
---------------------------------------------------------------
Yes, it can be an automatic module. But as I said previously, I suspect this
will cause problems for anyone trying to implement the log4j API where the
implementation is in a module, since the Log4j API locates the implementation
via ServiceLoader.
FWIW - I noticed that changes were made yesterday for the next version of
Logback to include a module-info.java. It will require SLF4J 1.8.x.
was (Author: ralph.go...@dslextreme.com):
Yes, it can be an automatic module. But as I said previously, I suspect this
will cause problems for anyone trying to implement the log4j API where the
implementation is in a module, since the Log4j API locates the implementation
via ServiceLoader.
> 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)
