SLF4J

General

Category
Free
Tag
Logging
License
MIT License
Registered
Jul 5, 2014
Favorites
0
Link
https://github.com/qos-ch/slf4j
See also
hugo
Logger
xLog
jodamoblog
Frodo

Additional

Language
Java
Version
v_1.7.22 (Dec 13, 2016)
Created
Aug 20, 2009
Updated
Apr 12, 2020
Owner
QOS.CH Sarl (qos-ch)
Contributors
Dale Wijnand (dwijnand)
Xavier Dury (kalgon)
Ceki Gulcu (ceki)
Craig P. Motlin (motlin)
Sebastian Schuberth (sschuberth)
Tobias Bieniek (Turbo87)
William Delanoue (twillouer)
Matteo Boffo aka stempelo (stempelo)
Mikhail Mazurskiy (ash2k)
Sebastian (sebkur)
Alex Panchenko (panchenko)
Valerii Pekarskyi (Larry0ua)
Björn Kautler (Vampire)
Alexander Dorokhine (adorokhine)
mciezadlo
Jeremy Landis (hazendaz)
Cédrik (javabean)
Libor Jelinek (bircow)
Show all (55)55
Activity
Badge
Generate
Download
Source code

Promotion

About SLF4J

The Simple Logging Facade for Java (SLF4J) serves as a simple facade or abstraction for various logging frameworks (e.g. java.util.logging, logback, log4j) allowing the end user to plug in the desired logging framework at deployment time. More information can be found on the SLF4J website.

Build Status

How to build SLF4J

SLF4J uses Maven as its build tool.

All versions upto and including 1.7.x require Java 5 or later to build. SLF4J version 2.0.x requires Java 9 or later.

How to contribute pull requests

If you are interested in improving SLF4J, that is great! The SLF4J community looks forward to your contribution. Please follow this process:

  1. Start a discussion on the slf4j-dev mailing list about your proposed change. Alternately, file a bug report to initiatite the discussion. Note that we usually ask most pull requests to be linked to a Jira ticket.

  2. Fork qos-ch/slf4j. Ideally, create a new branch from your fork for your contribution to make it easier to merge your changes back.

  3. Make your changes on the branch you hopefuly created in Step 2. Be sure that your code passes existing unit tests. Please add unit tests for your work if appropriate. It usually is.

  4. Push your changes to your fork/branch in github. Don't push it to your master! If you do it will make it harder to submit new changes later.

  5. Submit a pull request to SLF4J from from your commit page on github.

  6. Did we mention that you will be asked to link your pull request with a Jira ticket?