Android and Log4j
ralph.goers at dslextreme.com
Sun Dec 3 20:08:56 UTC 2017
> On Dec 3, 2017, at 12:19 PM, Alan Bateman <Alan.Bateman at oracle.com> wrote:
> On 03/12/2017 18:25, Ralph Goers wrote:
>> Log4j added support for Java 9 by:
>> Converting the Log4j-API jar to a multi-release jar that includes support for StackWalker and the new Process Id support.
>> Adding a module-info.jar to the Log4j API jar.
>> We are now getting complaints from Android users (as well as a few others) that their tools no longer work with log4j. During development I ran into problems with OSGi. The problems seem to mostly revolve around the fact that they can’t deal with the classes for Java 9. I was surprised that Android is failing on the classes in META-INF/versions/9 as I had assumed that would be an invalid location for a class file prior to Java 9, but that seems not to be the case. The fact that module-info.java turns into a class file also seems to be a problem since the various tools are seeing it and having problems with it.
>> Do you have any recommendations on how we can resolve this impasse?
> The Android tools should ignore class files in META/**, at least until they are updated to work with multi-release JARs. Have you created a bug for them to look at this issue?
Yes, although I don’t develop for Android so I am not certain I created the issue correctly. https://issuetracker.google.com/u/1/issues/70118537 <https://issuetracker.google.com/u/1/issues/70118537>.
I also created https://issues.apache.org/jira/browse/FELIX-5592 <https://issues.apache.org/jira/browse/FELIX-5592> which relates to https://issues.apache.org/jira/browse/FELIX-5527 <https://issues.apache.org/jira/browse/FELIX-5527>. No activity has occurred on either of these issues.
More information about the core-libs-dev