[jira] [Resolved] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

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

     [ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralph Goers resolved LOG4J2-2041.
---------------------------------
    Resolution: Won't Fix

Log4j 2 uses a multi-release jar for log4j-api. The jar contains 2 classes that were compiled with Java 9 in the META-INF/versions directory. This was never a valid place to put class files and utilities should be ignoring that directory. Furthermore, Java 9 will be released on September 21 - 11 days from now. Given that processing stack traces is slower in Java 9 without using the new StackWalker class (which is much faster) removing the two added classes is not going to happen.

> 2.9.0 contains classes built to class version 53
> ------------------------------------------------
>
>                 Key: LOG4J2-2041
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2041
>             Project: Log4j 2
>          Issue Type: Bug
>    Affects Versions: 2.9.0
>            Reporter: William Ferguson
>
> 2.9.0 is built to class version 53, presumably because it includes attempts at support for JDK9.
> But JDK has not been released yet, so build tools that introspect class files (such as Proguard) do not yet support consuming version 53 classes.
> Can I suggest that an appropriate forward path is to build using and against JDK9 but to build to class version 52 until some time after JDK9 has been released so as to not break existing tooling.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)