When using SLF4J in an OSGi environment, the wiring can go wrong because SLF4J does not include uses clauses in the MANIFEST.MF.

This leads to errors like:

 loader constraint violation:
when resolving method 'org.slf4j.ILoggerFactory org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()'
the class loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @3a07fd19 of the current class,
org/slf4j/LoggerFactory, and
the class loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @773560cf for the method's defining class,
org/slf4j/impl/StaticLoggerBinder,
have different Class objects for the type org/slf4j/ILoggerFactory used in the signature
(org.slf4j.LoggerFactory is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @3a07fd19,
parent loader 'platform';
org.slf4j.impl.StaticLoggerBinder is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @773560cf,
parent loader 'platform')