Home | History | Annotate | only in /external/slf4j
Up to higher level directory
NameDateSize
.gitattributes21-Oct-2016483
.gitignore21-Oct-2016143
.idea/21-Oct-2016
.travis.yml21-Oct-201664
binderVersion.pl21-Oct-2016740
codeStyle.xml21-Oct-201630.5K
goVersion.sh21-Oct-2016226
integration/21-Oct-2016
jcl-over-slf4j/21-Oct-2016
jul-to-slf4j/21-Oct-2016
LICENSE.txt21-Oct-20161.1K
log4j-over-slf4j/21-Oct-2016
MODULE_LICENSE_MIT21-Oct-20160
NOTICE21-Oct-20161.1K
osgi-over-slf4j/21-Oct-2016
pom.xml21-Oct-201611.2K
README.md21-Oct-20161.3K
slf4j-android/21-Oct-2016
slf4j-api/21-Oct-2016
slf4j-ext/21-Oct-2016
slf4j-jcl/21-Oct-2016
slf4j-jdk14/21-Oct-2016
slf4j-log4j12/21-Oct-2016
slf4j-migrator/21-Oct-2016
slf4j-nop/21-Oct-2016
slf4j-simple/21-Oct-2016
slf4j-site/21-Oct-2016
src/21-Oct-2016
test21-Oct-20160
version.pl21-Oct-2016771

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