> On Jul 9, 2017, at 11:45 AM, Gary Gregory <[email protected]> wrote: > > On Sun, Jul 9, 2017 at 10:49 AM, Ralph Goers <[email protected]> > wrote: > >> When I investigated logging on android I came to the conclusion that the >> only usable logging that can be done in android is with the implementation >> that Google provides. I have no problem creating a Log4J jar for android >> but I am not willing to not support Java 9 to do it. >> > > I am sorry but that feels a bit disingenuous to me. > > I have not heard anyone say we should not support Java 9, which ATM is just > an optimization, not something that is _required_ for Log4j to run on Java > 9. > > We support Java 9 already in 2.8.2: the code should runs when Java 9 comes > out if you use whatever unlocking command line options Java 9 provides WRT > modules, reflection, and who knows what other horrors of backwards > incompatibility Oracle has decided to put in there. Yes, kudos to Google > for adding Kotlin support. > > I've proposed we optimize for Java 9 it in a separate log4j-api-jar that an > Android developer would obviously not use; a jar for which we already have > a module. I am no Android expert, but I've not found a way to exclude the > Java 9 code from an Android build, maybe that's possible, who knows.
Let me be blunt. I am -1 on removing the StackWalker code. I am quite sure that I could create a log4j-api-android jar that does not include Stackwalker. In fact, it would be trivial. > > A real life problem is when Log4j is brought in as a third party > dependency, then you're up the proverbial creek. > > Gary > Ralph
