Home | History | Annotate | only in /external/slf4j
Up to higher level directory
NameDateSize
.gitattributes05-Oct-2017483
.gitignore05-Oct-2017143
.idea/05-Oct-2017
.travis.yml05-Oct-201764
Android.mk05-Oct-20171.5K
binderVersion.pl05-Oct-2017740
codeStyle.xml05-Oct-201730.5K
goVersion.sh05-Oct-2017226
integration/05-Oct-2017
jcl-over-slf4j/05-Oct-2017
jul-to-slf4j/05-Oct-2017
LICENSE.txt05-Oct-20171.1K
log4j-over-slf4j/05-Oct-2017
MODULE_LICENSE_MIT05-Oct-20170
NOTICE05-Oct-20171.1K
osgi-over-slf4j/05-Oct-2017
pom.xml05-Oct-201711.2K
README.md05-Oct-20171.3K
slf4j-android/05-Oct-2017
slf4j-api/05-Oct-2017
slf4j-ext/05-Oct-2017
slf4j-jcl/05-Oct-2017
slf4j-jdk14/05-Oct-2017
slf4j-log4j12/05-Oct-2017
slf4j-migrator/05-Oct-2017
slf4j-nop/05-Oct-2017
slf4j-simple/05-Oct-2017
slf4j-site/05-Oct-2017
src/05-Oct-2017
test05-Oct-20170
version.pl05-Oct-2017771

README.md

      1 # About SLF4J
      2 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.
      3 More 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
      8 If you are interested in improving SLF4J, great! The SLF4J community looks forward to your contribution. Please follow this process:
      9 
     10 1. 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).
     11 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.
     12 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.
     13 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.
     14 5. Submit a pull request to SLF4J from from your commit page on github.
     15