David Beaumont

You've already raised this.

True, but fixing one will inevitably fix the other. SLF4J + log4J2 backend is going to be almost exactly the same same code, just with a very thin layer in...

The issue is that if there SLF4J API was not written to expect to be called from another logging API we might never be able to address things like the...

Hi, thanks for your comments (and sorry for not replying sooner). I assume you mean that there are multiple calls to "isLoggable()" for the same log statement when you talk...

The log context logs to the backend of the logger it was created with. And that field is final, so cannot change. If a composite logger backend wishes to allow...

Yes, but when logging, the cost of doing the second check is utterly insignificant to the rest of the work done. Optimizing for "no work" only matters in the case...

Thanks for this information, it's hopefully going to be useful to anyone else. The fact is that Google doesn't really use log4j or logback, so there's been no effort internally...

I've just looked at logback and it's licensed under the LGPL and EPL (simultaneously), but not ASL. While it's still possible to have a Google project depend on software developed...

Rather than describe the change you think you want, can you describe the effect you wish to see? There may be many ways to achieve what you want, and it's...

I'm in the middle of doing a doc about this sort of customization, but it's not ready yet so I can try to summarize. If the resource key is just...