Pax Logging 2 Released!

Pax Logging team is proud to announce Pax Logging 2 release. Due to unforeseen shading problem, initial 2.0.0 release had JDK11 failure, so the Pax Logging 2 has version 2.0.1…

The most important feature of this release is support for OSGi R7 logging package (org.osgi.service.log version 1.4). Pax Logging itself was always more about using standard, non-OSGI specific facades to logging mechanisms, but now, standard org.osgi.service.log.Logger interface can be used as well.

This is new R7 way to use loggers:

org.osgi.framework.BundleContext context = ...; ServiceReference<org.osgi.service.log.LoggerFactory> sr = context.getServiceReference(org.osgi.service.log.LoggerFactory.class); org.osgi.service.log.LoggerFactory factory = context.getService(sr); org.osgi.service.log.Logger log = factory.getLogger("my.logger");"INFO through R7 org.osgi.service.log.Logger"); log.audit("AUDIT through R7 org.osgi.service.log.Logger");

Just like Pax Logging 1.11.x, 2.x line comes with huge refactoring and unification of internal mechanism + more than 100 integration tests that were not present before 1.11.x.

OSGi R7 specification introduces two additional packages:

  • org.osgi.service.log.admin (

    PAXLOGGING-267 - Getting issue details... STATUS


    PAXLOGGING-268 - Getting issue details... STATUS

These packages are not yet implemented by Pax Logging 2.0.1. Pax Logging exposes (that was one of initial design goals) configuration of underlying logging framework through Configuration Admin and org.osgi.service.log.admin is not straightforward to implement assuming this requirement. PAXLOGGING Jira issues for the above package implementations are the only issues left to be done (as of 2020-01-13).

Here’s full list of Jira issues resolved:

key summary type created assignee reporter priority status resolution