That would definitely duplicate effort. I've seen a few libraries out there that abstract out logging only to make the default implementation slf4j or log4j-api which just makes yet another hop of indirection.
On 3 September 2017 at 13:05, Gary Gregory <garydgreg...@gmail.com> wrote: > On Sep 3, 2017 12:00, "Thomas Vandahl" <t...@apache.org> wrote: > > On 03.09.17 09:02, Romain Manni-Bucau wrote: > > Once again the issue is the risk to break users and to ensure the api is > > consistent accross all libs (jcs, openjpa, tomee, cxf, activemq, commons, > > ...). It is clearly not "is it good or bad" and tomee switch from log4j1 > to > > jul reduced the number of issues about the logging quite a lot and > increase > > the logging consistency. There is no free lunch ;). > > I guess the only real solution is a logging stub in JCS that can be tied > to any logging sub-system by configuration. It's not that difficult to do. > > > Would that not duplicate what logging facades (like log4j-api) already > provide? > > Gary > > > Bye, Thomas. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > -- Matt Sicker <boa...@gmail.com>
