; > On Oct 7, 2018, at 3:26 AM, Rob Gansevles wrote:
> >
> > Wrapping the LoaderUltil (log4j-api) calls in Loader (log4j-core) like
> > below does work, I can load classes in core when I replace
> > LoaderUtil.newCheckedInstanceOfProperty()
> > with the proposed
by default. If it's
> >> not
> >>> set right, you can use of the methods there to specify the correct
> >>> ClassLoader, or you can even push and pop TCCLs essentially.
> >>>
> >>> On Wed, 3 Oct 2018 at 16:46, Ralph Goers
> >> w
the loading it is causing the
> problem. That means we are either doing the loading wrong or there is
> something broken in OSGi.
> >
> > Ralph
> >
> >> On Sep 28, 2018, at 10:20 AM, Rob Gansevles
> wrote:
> >>
> >> Yes, that makes sense, but it
der.java:411)
at
org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
On Fri, Sep 28, 2018 at 6:01 PM Ralph Goers
wrote:
> All ContextSelectors are part of log4j-core, not log4j-api.
>
> Ralph
>
> > On Sep 2
Hi,
I would like to use the BasicContextSelector in our OSGI application so
have a single global log4j connfiguration as described in
http://logging.apache.org/log4j/2.x/manual/logsep.html
However, BasicContextSelector lives in
package org.apache.logging.log4j.core.selector which does not seem to
on’t know when. Between
> work and the other things I am trying to do for logging I don’t have much
> time. I’ll take a look at that link.
>
> Ralph
>
> > On Feb 21, 2018, at 3:37 PM, Rob Gansevles wrote:
> >
> > Ralph,
> >
> > Do you think that release 2.10 b
21, 2018 at 2:12 AM, Ralph Goers
wrote:
> 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 tryin
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 mess
