[jira] [Comment Edited] (LOG4J2-2133) Log4J 2 appears incompatible with Android platform due to inclusion of Java 9 classes (class file version 53)

["Ralph Goers (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16275995#comment-16275995 ] 

Ralph Goers edited comment on LOG4J2-2133 at 12/3/17 4:47 PM:
--------------------------------------------------------------

[~olegk] I think this problem is going to get worse for Android users before it gets better. Adding a module-info.java file to support a jar as a Java 9 module is just beginning to happen and I believe it will only increase. In fact, it is surprising that HttpClient isn't looking to do that, since lots of components use it. It is unfortunate that Oracle decided to use a Java file instead of a JSON file, but we can't change it now. Log4j 1.8.x actually added a module-info.java file before Log4j did. So while you may be able to use SLF4J 1.7.x for a while, users will not be able to upgrade without encountering the same problem you are experiencing with Log4j.

I suspect the only solution we will be able to have for this is to either have a separate jar for Android, which will admittedly be a pain, but since they seem to be stuck in the past I don't see any way around it.

Suggestions are welcome.


was (Author: ralph.goers@dslextreme.com):
[~olegk] I think this problem is to get worse for Android users before it gets better. Adding a module-info.java file to support a jar as a Java 9 module is just beginning to happen and I believe it will only increase. In fact, it is surprising that HttpClient isn't looking to do that, since lots of components use it. It is unfortunate that Oracle decided to use a Java file instead of a JSON file, but we can't change it now. Log4j 1.8.x actually added a module-info.java file before Log4j did. So while you may be able to use SLF4J 1.7.x for a while, users will not be able to upgrade without encountering the same problem you are experiencing with Log4j.

I suspect the only solution we will be able to have for this is to either have a separate jar for Android, which will admittedly be a pain, but since they seem to be stuck in the past I don't see any way around it.

Suggestions are welcome.

> 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)