On Thu, Aug 15, 2019 at 11:38 AM Carsten Ziegeler <cziege...@apache.org> wrote: > > Am 15.08.2019 um 11:21 schrieb Robert Munteanu: > > On Thu, 2019-08-15 at 11:12 +0200, Carsten Ziegeler wrote: > >> Hi Roy, > >> > >> I guess my mail is a little bit misleading :) > >> > >> It's totally fine to use SLF4J directly and we should keep doing > >> this. > >> Under the covers, everything you log to slf4j is routed through the > >> LogService so other components in the system can listen to log > >> entries etc. > >> > >> So this is about keeping everything as is for clients doing logging > >> but > >> just replace the LogService implementation with the Apache Felix one > >> - > >> and make sure that we still have todays features in place. > > > > +1 from me. I also asked about this a year ago :-) > > > > > > https://lists.apache.org/thread.html/581b9ac69bfa6a8692e6bffc98fe5fdd6f5b4c35989d6b53841f7f10@%3Cdev.sling.apache.org%3E > > > That's actually a different ask :) > > We have o.a.s.commons.logservice which is an OSGi R6 LogService > implementation *and* a log listener logging everything to slf4j. My > suggestion is to replace the LogService impl with Apache Felix Log and > keep the listener.
I think that would be a good start! +1 > Our logback integration is o.a.s.commons.log which I think is similar to > the logback stuff in Apache Felix. > > Now maybe we can replace all of our stuff with the things from Felix? That would be even better - but like I mentioned in thread pointed out by Robert, I don't know enough about it to say what (or whether) that is possible. regards, Karl > Carsten > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org -- Karl Pauls karlpa...@gmail.com