Hi. I had some problems with the startup messages from pax logging. It seemed to be logged in a seperate way when I loaded pax-logging-api bundle first. Seems that you have to start pax-logging-service before pax-logging-api to be able to filter startup messages like "Enabling SLF4J API support." etc. Is this right?
What about providing a "uber bundle" containing both pax-logging-api and pax-logging-service? Looked at this, but seems that the package org.ops4j.pax.logging.internal is in both bundles. And the actual activator (org.ops4j.pax.logging.internal.Activator) is in both bundles (with different code). Would be nice if pax-logging-api and pax-logging-service had different java namespaces. WDYT? Regards, Sten Roger Sandvik
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
