Skip to content

An adapter to use LOGBACK as service provider and runtime log engine for the ELF4J (Easy Logging Facade for Java) API

License

Notifications You must be signed in to change notification settings

elf4j/elf4j-logback

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

elf4j-logback

An adapter to use LOGBACK as service provider and runtime log engine for the ELF4J (Easy Logging Facade for Java) API

User Story

As an application developer using the ELF4J API, I want to have the option of selecting LOGBACK as my log engine, at application deploy time without code change or re-compile.

Prerequisite

Java 8+

Get It...

Maven Central

Use It...

If you are using the ELF4J API for logging, and wish to select or change to use LOGBACK as the run-time log engine, then simply pack this service provider in the classpath when the application deploys. No code change needed. At compile time, the client code is unaware of this run-time logging service provider. With the ELF4J facade, opting for LOGBACK as the logging implementation is a deployment-time decision.

The usual LOGBACK configuration applies.

With Maven, in addition to use compile-scope on the ELF4J API dependency, an end-user application would use runtime-scope for this provider as a dependency:

<dependency>
    <groupId>io.github.elf4j</groupId>
    <artifactId>elf4j</artifactId>
    <scope>compile</scope>
</dependency>

<dependency>
    <groupId>io.github.elf4j</groupId>
    <artifactId>elf4j-logback</artifactId>
    <scope>runtime</scope>
</dependency>