log4j-to-slf4j not working with slf4j v2 about logging-log4j2 HOT 5 CLOSED

@HannesWell,

Sure, PRs are welcome. We use maven-bundle-plugin to generate the OSGI manifest.

from logging-log4j2.

By the way guys, just out of curiosity, how come this situation works for my library with logcaptor using slf4j v2 and latest version of log4j-to-slf4j, but not working for the OSGi world?

Because non OSGi applications usually don't care about the OSGi metadata. But the OSGi metadata said that log4j-to-slf4j required slf4j in version [1.7,2). Therefore an OSGi runtime refused to resolve the log4j.to-slf4j if only slf4j 2.0.x is available.

from logging-log4j2.

Nevermind, I had a dependency management issue with dependencies having different versions. There is no issue, so I am closing it.

from logging-log4j2.

In the OSGi world it is currently indeed impossible to use log4j-to-slf4j in conjunction with slf4j-2 because the Manifest only imports the slf4j packages only up until, but excluding 2:

Import-Package:
 [...]
 org.slf4j;version="[1.7,2)",
 org.slf4j.spi;version="[1.7,2)"

If log4j-to-slf4j works well with slf4j 1 and 2 I suggest to widen the package import range to "[1.7,3)".
If the log4j maintainers are interested I can provide a corresponding PR.

from logging-log4j2.

By the way guys, just out of curiosity, how come this situation works for my library with logcaptor using slf4j v2 and latest version of log4j-to-slf4j, but not working for the OSGi world?

from logging-log4j2.