> can you check if JUL packages really comes from Pax Logging ?
Err, how can they? Perhaps I'm misunderstanding.
Surely the java.util.logging packages are provided by the JRE?
I DO have one log message that DOES come out. Very odd.
If I step through the code in the debugger, I appear to have two code paths.
In one, my calls to java.util.logging.Logger.info end up in
org.ops4j.pax.logging.log4j2.internal.JdkHandler.
Later a call to java.util.logging.Logger.info ends up in
org.ops4j.pax.logging.service.internal.JdkHandler
These log calls end up being passed through to log4j, rather than log4j2. log4j
isn't set up at all, only log4j2 is set up, so these messages don't come out.
So for some reason, we have the "log4j" pax logging bundle ("OPS4J Pax Logging
- Service", "org.ops4j.pax.logging.pax-logging-service") AS WELL as the log4j2
logging bundle ("OPS4J Pax Logging - Log4j v2",
"org.ops4j.pax.logging.pax-logging-log4j2"). Not sure where that's come from,
but that doesn't appear in the standard karaf distro. I don't believe we
explicitly list that anywhere as a requirement so at the moment I'm not sure
how I determine what has caused that to be included by the distribution build
process.
