[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276026#comment-16276026 ]
Ralph Goers edited comment on LOG4J2-2133 at 12/3/17 6:33 PM: -------------------------------------------------------------- [~jvz] We definitely should link to upstream tickets as well as open tickets against the offending tools - as I did for the Maven bundle plugin, but that alone won't satisfy users whose stuff isn't working now. Yes, trying to come up with hacks around the decision to have module-info be a class file is almost certainly a fools errand as it would probably break more stuff than it "fixes". As far as module-info.java goes, the only thing I can think of to do is to remove module-info.java and just use the manifest entry to have it be a named automatic module as our other jars are. Eventually this may be a problem since it is using ServiceLoader and it might need to find the implementation of the service in a module. was (Author: ralph.go...@dslextreme.com): [~jvz] We definitely should link to upstream tickets as well as open tickets against the offending tools - as I did for the Maven bundle plugin, but that alone won't satisfy users whose stuff isn't working now. Yes, trying to come up with hacks around the decision to have module-info be a class file is almost certainly a fools errand as it would probably break more stuff than it "fixes". > 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)