NameDateSize

..10-Aug-201812 KiB

.gitattributes10-Aug-2018483

.gitignore10-Aug-2018143

.idea/10-Aug-20184 KiB

.travis.yml10-Aug-201864

Android.mk10-Aug-20181.4 KiB

binderVersion.pl10-Aug-2018740

codeStyle.xml10-Aug-201830.5 KiB

goVersion.sh10-Aug-2018226

integration/10-Aug-20184 KiB

jcl-over-slf4j/10-Aug-20184 KiB

jul-to-slf4j/10-Aug-20184 KiB

LICENSE.txt10-Aug-20181.1 KiB

log4j-over-slf4j/10-Aug-20184 KiB

MODULE_LICENSE_MIT10-Aug-20180

NOTICE10-Aug-20181.1 KiB

osgi-over-slf4j/10-Aug-20184 KiB

pom.xml10-Aug-201811.2 KiB

README.md10-Aug-20181.3 KiB

slf4j-android/10-Aug-20184 KiB

slf4j-api/10-Aug-20184 KiB

slf4j-ext/10-Aug-20184 KiB

slf4j-jcl/10-Aug-20184 KiB

slf4j-jdk14/10-Aug-20184 KiB

slf4j-log4j12/10-Aug-20184 KiB

slf4j-migrator/10-Aug-20184 KiB

slf4j-nop/10-Aug-20184 KiB

slf4j-simple/10-Aug-20184 KiB

slf4j-site/10-Aug-20184 KiB

src/10-Aug-20184 KiB

test10-Aug-20180

version.pl10-Aug-2018771

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