Go to file
Ceki Gulcu 3ec4456cd3 correct site id in distributionManagement 2016-12-13 18:05:25 +01:00
.idea use 2 space indentation in IntelliJ formatter 2014-12-13 19:13:53 +01:00
integration prepare release 1.7.22 2016-12-13 18:02:38 +01:00
jcl-over-slf4j prepare release 1.7.22 2016-12-13 18:02:38 +01:00
jul-to-slf4j prepare release 1.7.22 2016-12-13 18:02:38 +01:00
log4j-over-slf4j prepare release 1.7.22 2016-12-13 18:02:38 +01:00
osgi-over-slf4j prepare release 1.7.22 2016-12-13 18:02:38 +01:00
slf4j-android prepare release 1.7.22 2016-12-13 18:02:38 +01:00
slf4j-api prepare release 1.7.22 2016-12-13 18:02:38 +01:00
slf4j-ext prepare release 1.7.22 2016-12-13 18:02:38 +01:00
slf4j-jcl prepare release 1.7.22 2016-12-13 18:02:38 +01:00
slf4j-jdk14 prepare release 1.7.22 2016-12-13 18:02:38 +01:00
slf4j-log4j12 prepare release 1.7.22 2016-12-13 18:02:38 +01:00
slf4j-migrator prepare release 1.7.22 2016-12-13 18:02:38 +01:00
slf4j-nop prepare release 1.7.22 2016-12-13 18:02:38 +01:00
slf4j-simple prepare release 1.7.22 2016-12-13 18:02:38 +01:00
slf4j-site prepare release 1.7.22 2016-12-13 18:02:38 +01:00
src/main mark 1.7.6-SNAPSHT, added missing modules to assembly source file 2013-03-27 16:13:45 +01:00
.gitattributes Add git attributes 2014-09-26 23:33:52 -04:00
.gitignore add mac os x metadata file .DS_Store to .gitignore 2013-03-27 03:13:34 +04:00
.travis.yml send travis notification to a different email address 2016-02-11 22:26:43 +01:00
LICENSE.txt Update LICENSE.txt 2014-04-26 22:32:24 +05:30
README.md Set up Travis CI for SLF4J. 2014-11-27 11:53:10 -08:00
codeStyle.xml Reformat all code with the exception of the slf4j-android module to use 4 space indentation and max line width of 160. 2015-03-26 12:59:25 +01:00
pom.xml correct site id in distributionManagement 2016-12-13 18:05:25 +01:00
test testing 2009-10-01 18:01:15 +02:00

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.