* When I said "Java 9 has been on the roadmap" I meant the Log4j 2 roadmap.
On Sun, Jul 9, 2017 at 9:15 PM, Remko Popma <[email protected]> wrote: > Not sure I agree. Our interest in Android is a very recent thing. We've > done some work with LOG4J2-1926 > <https://issues.apache.org/jira/browse/LOG4J2-1926>, we are still > discovering new work and I suspect we will keep discovering new issues as > we start to take an in-depth look. If anything, let's make Android the > "theme" for Log4j 2.10. > > Java 9 has been on the roadmap for a long time and is finally in a state > where we can start asking for user feedback on it. > I don't mind that Java 9 is still not officially released yet; it gives us > some wiggle room in case we need to make changes. > > But I do like the version number symmetry: "Log4j offers Java 9 support > from version 2.9". Call me a poet. :-) > > > > On Sun, Jul 9, 2017 at 8:13 PM, Mikael Ståldal <[email protected]> wrote: > >> As far as I understand, Java 9 will be released September 21. >> >> Now we plan to release Log4j 2.9 before the end of July. >> >> Given the problems that Java 9 causes, at least for Android, I suggest >> that we de-scope the Java 9 specific stuff (StackLocator) from the 2.9 >> release. >> >> It should be possible to do a 2.10 release with the Java 9 specific stuff >> before September 21, right? And if not, that's not a disaster since the 2.9 >> release will still work with Java 9 (just with non-optimal performance for >> locationInfo), right? >> >> I would say it's more important that log4j-api works on Android than we >> get optimal performance for locationInfo on Java 9. Especially now when >> Java 9 is not even officially released. >> > >
