Google Git
Sign in
android / platform / external / slf4j / c068a727ec37be5e017a5cad233e979286ff245e
commitc068a727ec37be5e017a5cad233e979286ff245e[log] [tgz]
authorBob Badour <[email protected]>Fri Mar 04 08:50:51 2022 +0000
committerAutomerger Merge Worker <[email protected]>Fri Mar 04 08:50:51 2022 +0000
treeda3f32d164f0d6683f29351262ebade77cfdac12
parenta7078ad77d2aed71a108a67af27f11f7f74c8a1e [diff]
parenteecd299d4e9d29efb6d9c87a5fe7cfc67c0c4ab6 [diff]
Move comment to license_note am: 4a0afbed85 am: 9057c64dfe am: cd1528b150 am: e623afa002 am: eecd299d4e

Original change: https://android-review.googlesource.com/c/platform/external/slf4j/+/2006854

Change-Id: Ia2762c4a31e682fbd7f9023215888fc4c5c99c73
tree: da3f32d164f0d6683f29351262ebade77cfdac12
  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. METADATA
  27. MODULE_LICENSE_MIT
  28. NOTICE
  29. OWNERS
  30. pom.xml
  31. README.md
  32. test
  33. 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.