• Home
  • Annotate
  • current directory
Name Date Size

..05-Dec-2017-

.idea/05-Dec-2017-

integration/05-Dec-2017-

jcl-over-slf4j/05-Dec-2017-

jul-to-slf4j/05-Dec-2017-

log4j-over-slf4j/05-Dec-2017-

osgi-over-slf4j/05-Dec-2017-

slf4j-android/05-Dec-2017-

slf4j-api/05-Dec-2017-

slf4j-ext/05-Dec-2017-

slf4j-jcl/05-Dec-2017-

slf4j-jdk14/05-Dec-2017-

slf4j-log4j12/05-Dec-2017-

slf4j-migrator/05-Dec-2017-

slf4j-nop/05-Dec-2017-

slf4j-simple/05-Dec-2017-

slf4j-site/05-Dec-2017-

src/main/05-Dec-2017-

.gitattributes A D05-Dec-2017483

.travis.yml A D05-Dec-201764

Android.mk A D05-Dec-20171.5 KiB

LICENSE.txt A D05-Dec-20171.1 KiB

MODULE_LICENSE_MIT A D05-Dec-20170

NOTICE A D05-Dec-20171.1 KiB

README.md A D05-Dec-20171.3 KiB

binderVersion.pl A D05-Dec-2017740

codeStyle.xml A D05-Dec-201730.5 KiB

goVersion.sh A D05-Dec-2017226

pom.xml A D05-Dec-201711.2 KiB

test A D05-Dec-20170

version.pl A D05-Dec-2017771

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