[automerger skipped] DO NOT MERGE - Merge pi-dev@5234907 into stage-aosp-master
am: e30ddec72b -s ours
am skip reason: subject contains skip directive

Change-Id: I7d31b1c79a54e809d8d9fe432f941010271f26ba
tree: 4350563157199e968dcb97546b8a0386ae3cd1d8
  1. .gitattributes
  2. .gitignore
  3. .idea/
  4. .travis.yml
  5. Android.bp
  6. LICENSE.txt
  10. README.md
  11. binderVersion.pl
  12. codeStyle.xml
  13. goVersion.sh
  14. integration/
  15. jcl-over-slf4j/
  16. jul-to-slf4j/
  17. log4j-over-slf4j/
  18. osgi-over-slf4j/
  19. pom.xml
  20. slf4j-android/
  21. slf4j-api/
  22. slf4j-ext/
  23. slf4j-jcl/
  24. slf4j-jdk14/
  25. slf4j-log4j12/
  26. slf4j-migrator/
  27. slf4j-nop/
  28. slf4j-simple/
  29. slf4j-site/
  30. src/
  31. test
  32. version.pl

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.