You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
sandy 99da0f2c72 pl286 release code 4 years ago
..
.idea pl286 release code 4 years ago
integration pl286 release code 4 years ago
jcl-over-slf4j pl286 release code 4 years ago
jul-to-slf4j pl286 release code 4 years ago
log4j-over-slf4j pl286 release code 4 years ago
osgi-over-slf4j pl286 release code 4 years ago
slf4j-android pl286 release code 4 years ago
slf4j-api pl286 release code 4 years ago
slf4j-ext pl286 release code 4 years ago
slf4j-jcl pl286 release code 4 years ago
slf4j-jdk14 pl286 release code 4 years ago
slf4j-log4j12 pl286 release code 4 years ago
slf4j-migrator pl286 release code 4 years ago
slf4j-nop pl286 release code 4 years ago
slf4j-simple pl286 release code 4 years ago
slf4j-site pl286 release code 4 years ago
src/main pl286 release code 4 years ago
.gitattributes pl286 release code 4 years ago
.travis.yml pl286 release code 4 years ago
Android.mk pl286 release code 4 years ago
LICENSE.txt pl286 release code 4 years ago
MODULE_LICENSE_MIT pl286 release code 4 years ago
NOTICE pl286 release code 4 years ago
README.md pl286 release code 4 years ago
binderVersion.pl pl286 release code 4 years ago
codeStyle.xml pl286 release code 4 years ago
goVersion.sh pl286 release code 4 years ago
pom.xml pl286 release code 4 years ago
test pl286 release code 4 years ago
version.pl pl286 release code 4 years ago

README.md

About SLF4J

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. More information can be found on the SLF4J website.

Build Status

Build Status

How to contribute pull requests

If you are interested in improving SLF4J, great! The SLF4J community looks forward to your contribution. Please follow this process:

  1. Start a discussion on the slf4j-dev mailing list about your proposed change. Alternately file a bug report.
  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.
  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.
  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.
  5. Submit a pull request to SLF4J from from your commit page on github.