avaje-slf4j-jpl

Adapts Java platform logging (System.Logger) to SLF4J 1.7.x.

Requires Java 11 or greater.

Step 1. Add dependency

<dependency>
  <groupId>io.avaje</groupId>
  <artifactId>avaje-slf4j-jpl</artifactId>
  <version>1.2</version>
</dependency>

Step 2. Edit module-info adding requires

When using module-info add requires io.avaje.logging.slf4j;

module ... {
  ...
  requires io.avaje.logging.slf4j;
}

for SLF4J 1.7.x

Provides an adapter for Java platform logging to SLF4J 1.7.x.

Adding this dependency to your project means that Java System.Logger log messages will go to a SLF4J 1.7 Logger (and then onto whatever logging backend your application has configured).

This works by registered a System.LoggerFinder that provides a System.Logger that is an adapter to SLF4J 1.7 Logger.

Do not use this when

• When using SLF4J 2.x, instead use org.slf4j : slf4j-jdk-platform-logging
• When already using another System.LoggerFinder like Log4J's org.apache.logging.log4j : log4j-jpl

Why not part of SLF4J project?

Ideally this would be part of the SLF4J project and at some point it might be. At the moment Ceki is not keen so until that changes we have io.avaje : avaje-slf4j-jpl for use with SLF4J 1.7.x.

SLF4J 2.x

Applications using SLF4J 2.x will NOT use this artifact but instead use the Java platform logging adapter provided by SLF4J.

That is, SLF4J 2.x provides an adapter for Java platform logging but this is not compatible with SLF4J 1.7.x. People that want to use Java platform logger with SLF4J 1.7 will need to either:

• Use this avaje-slf4j-jpl adapter or a similar adapter
• Have Java platform logging go to JUL (which it does by default) and then use the JUL-SLF4J bridge to forward the logging events to the logging backend.

The SLF4J 2.x provided adapter for Java platform logging is at: github / qos-ch / slf4j / slf4j-jdk-platform-logging