• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..--

.idea/22-Nov-2023-4848

integration/22-Nov-2023-1,212690

jcl-over-slf4j/22-Nov-2023-2,8811,094

jul-to-slf4j/22-Nov-2023-745412

log4j-over-slf4j/22-Nov-2023-3,0441,292

osgi-over-slf4j/22-Nov-2023-412196

slf4j-android/22-Nov-2023-1,088381

slf4j-api/22-Nov-2023-5,6242,347

slf4j-ext/22-Nov-2023-5,2782,575

slf4j-jcl/22-Nov-2023-1,040385

slf4j-jdk14/22-Nov-2023-1,474644

slf4j-log4j12/22-Nov-2023-1,413578

slf4j-migrator/22-Nov-2023-3,1211,498

slf4j-nop/22-Nov-2023-418200

slf4j-simple/22-Nov-2023-1,441715

slf4j-site/22-Nov-2023-7,7946,040

src/main/22-Nov-2023-374328

.gitD01-Jan-19700

.gitattributesD22-Nov-2023483 2320

.gitignoreD22-Nov-2023143 1413

.travis.ymlD22-Nov-202364 54

Android.mkD22-Nov-20231.4 KiB3617

LICENSE.txtD22-Nov-20231.1 KiB2518

MODULE_LICENSE_MITD22-Nov-20230

NOTICED22-Nov-20231.1 KiB2518

README.mdD22-Nov-20231.3 KiB1512

binderVersion.plD22-Nov-2023740 4332

codeStyle.xmlD22-Nov-202330.5 KiB296295

goVersion.shD22-Nov-2023226 86

pom.xmlD22-Nov-202311.2 KiB391338

testD22-Nov-20230

version.plD22-Nov-2023771 4533

README.md

1# About SLF4J
2The 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.
3More information can be found on the [SLF4J website](http://www.slf4j.org).
4# Build Status
5[![Build Status](https://travis-ci.org/qos-ch/slf4j.png)](https://travis-ci.org/qos-ch/slf4j)
6
7# How to contribute pull requests
8If you are interested in improving SLF4J, great! The SLF4J community looks forward to your contribution. Please follow this process:
9
101. Start a discussion on the [slf4j-dev mailing list](http://www.slf4j.org/mailing-lists.html) about your proposed change. Alternately file a [bug report](http://www.slf4j.org/bug-reporting.html).
112. Fork qos-ch/slf4j. Ideally, create a new branch from your fork for your contribution to make it easier to merge your changes back.
123. 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.
134. 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.
145. Submit a pull request to SLF4J from from your commit page on github.
15