Hi Andrew, it's not that relevant, we are beyond that point. Introducing SystemLogger is an implicit way to recognize that java.logging is a bad API and that the JDK should cut its ties to that API (when it's possible, i.e. when Logger is not part of the public API).
I see the SystemLogger API is a way to get logging info from the JDK and to redirect them to whatever logger i want, so one can have the JDK log info and the application log info at the same place. cheers, Rémi ----- Mail original ----- > De: "Andrew Dinn" <ad...@redhat.com> > À: "Alan Bateman" <alan.bate...@oracle.com> > Cc: jigsaw-dev@openjdk.java.net > Envoyé: Mercredi 22 Mars 2017 12:57:56 > Objet: Re: Better tools for adjusting to strong encapsulation > On 22/03/17 11:42, Alan Bateman wrote: >> On your comment about neglect then you might want to look at JEP 264 [1]. >> ... >> [1] http://openjdk.java.net/jeps/264 > > You might also want to look at this xkcd > > https://xkcd.com/927/ > > which is, perhaps, just as relevant. > > regards, > > > Andrew Dinn > ----------- > Senior Principal Software Engineer > Red Hat UK Ltd > Registered in England and Wales under Company Registration No. 03798903 > Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander