Re: Log4j 2.10 / slf4j 1.8 icw OSGI/Eclipse

Hi Ralph, I have a simple osgi plugin that just logs something to slf4j Logger in the Activator's bundle start method. When I install and start log4j-core-2.11.0.jar, log4j-api-2.11.0.jar, log4j-slf4j-impl-2.11.0.jar and slf4j-api-1.8.0-beta1.jar in a clean felix gogo shell, and then install and

Re: Log4j 2.10 / slf4j 1.8 icw OSGI/Eclipse

We have some unit tests that run to test our OSGi support and they are all passing. I don’t have anything that uses OSGi but I suppose if I can find a sample project I could give it a whirl. I just don’t know when. Between work and the other things I am trying to do for logging I don’t have

Re: Log4j 2.10 / slf4j 1.8 icw OSGI/Eclipse

Ralph, Do you think that release 2.10 broke OSGI support? Maybe you can try it out if you have time. It could be that the manifest has to be modified as described here: http://aries.apache.org/modules/spi-fly.html#specconf In that case i guess slf4j also needs to be changed. Rob On Wed, Feb

Re: Log4j 2.10 / slf4j 1.8 icw OSGI/Eclipse

I implemented the bindings for SLF4J 1.8 and they are in 2.10.0 but I have never tried it with OSGi. Ralph > On Feb 20, 2018, at 12:47 PM, Rob Gansevles wrote: > > Hi, > > I am trying to get Log4j 2.10 with slf4j 1.8 working in my eclipse plugin > project. > > Slf4j

Log4j 2.10 / slf4j 1.8 icw OSGI/Eclipse

Hi, I am trying to get Log4j 2.10 with slf4j 1.8 working in my eclipse plugin project. Slf4j 1.8 does not use the StaticLoggerBinder method anymore and it seems to me osgi was depending on that. It worked fine with Log4j 2.9 and slf4j 1.7 The error I get is the No-SLF4J-providers-were-found