Hello First - I've updated https://github.com/ops4j/org.ops4j.pax.logging#versions page which now marks only 2 versions as active. Here's more detailed explanation:
- versions 1.9.x and 1.10.x are pre-refactoring versions without any real integration tests - version 1.11.x and 1.12.x are both based on OSGi CMPN Log service 1.3, but version 1.11.x includes Log4j1 backend. I've decided to keep and maintain only version 1.12.x, because we don't want to use Log4j1 backend anymore. The Log4j1 API is still available though. So please use 1.12.x for Felix 5.6 / Karaf 4.2 - version 2.0.x (with Log4j1 backend) and 2.1.x (without Log4j1 backend) are based on OSGi CMPN Log service 1.4 and because Log service 1.5 is identical, I've decided to keep and maintain only version 2.2.x The most important change in 1.12.4 and 2.2.1 is related to SLF4J 2.x API support. Actually the interfaces didn't change since version 1.7.x, but there was a change with discovery of logging backend. Instead of static org.slf4j.impl.StaticLoggerBinder, SLF4J 2 now relies on /META-INF/services/org.slf4j.spi.SLF4JServiceProvider which is now providing org.ops4j.pax.logging.slf4j.PaxLoggingSLF4JServiceProvider service. >From the API point of view nothing has changed except that pax-logging-api now exports `org.slf4j` package with version 2.0.6 (in addition to version 1.4, 1.5, 1.6 and 1.7). That's important for OSGi bundles compiled with maven-bundle-plugin (or bnd-maven-plugin) with default configuration which would generate this import header: Import-Package: org.slf4j;version="[2.0,3.0)". This would cause problems before Pax Logging 2.2.1 and 1.12.4. All the release notes can be found using the following links: - 2.2.1: https://github.com/ops4j/org.ops4j.pax.logging/milestone/98?closed=1 - 1.12.4: https://github.com/ops4j/org.ops4j.pax.logging/milestone/105?closed=1 kind regards Grzegorz Grzybek
