Google Git
Sign in
android / platform / external / slf4j / d0e8adea7585daea26a5426f8cf681d70fdf44e9
commitd0e8adea7585daea26a5426f8cf681d70fdf44e9[log] [tgz]
authorBill Yi <[email protected]>Wed Oct 24 18:34:53 2018 -0700
committerandroid-build-merger <[email protected]>Wed Oct 24 18:34:53 2018 -0700
tree02871b43dd232af1503de2a4c23aa7defc49d920
parent874c6bdb07eed3a6936ef8309a0d4f7121553936 [diff]
parentfc550dd9c0df798dcff568fba74a23285369e421 [diff]
[automerger skipped] Merge pie-platform-release to aosp-master - DO NOT MERGE am: af8a97c803  -s ours
am: fc550dd9c0  -s ours

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