Am 16.01.2012 17:53, schrieb Stuart McCulloch:
You could always try unzipping the bundle and use the "strings"
command-line utility on each file to find out exactly which
class/resource inside it refers to org.slf4j.impl.
That's easy, it's a somewhat peculiar design decision of SLF4J:
org.slf4j.LoggerFactory calls
org.slf4j.impl.StaticLoggerBinder.getSingleton(). Each SLF4J binding
(slf4j-simple, slf4j-log4j12, logback etc.) contains its own copy of
StaticLoggerBinder.
The bindings are packaged as OSGi fragments. Not the best OSGi style,
but that way SLF4J works both in OSGi and non-OSGi environments.
Anyway, I've now changed the bnd directives in Pax URL to
Import-Package: ..., !org.slf4j.impl, *
so I hope that solves David's problem.
Best regards,
Harald
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
