Google Git
Sign in
android / platform / external / slf4j / refs/heads/android14-prebuilt-test
commit2e4c2ae3efcef989517deba4897a1ba8c3824b8b[log] [tgz]
authorAndrew Vuong <[email protected]>Wed Feb 22 21:23:01 2023 +0000
committerPresubmit Automerger Backend <android-build-presubmit-automerger-backend@system.gserviceaccount.com>Wed Feb 22 21:23:01 2023 +0000
treeafdfd3d5dcc7cf73aeccb4921633fdd7c086c47b
parent872658e782f631021da7317d115712b4af24f940 [diff]
parentcb5a367a79a71163d125e9f39c38e0c6727a61f6 [diff]
[automerged blank] Add visibility for OnDevicePersonalization and apache-velocity-engine. 2p: cb5a367a79

Blank merge reason: Change-Id I59a95fd8dc12fa5bfcda7f7824e19330a01a0ca8 with SHA-1 d659bd6d5f is in history

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

Bug: 262898801
Change-Id: I1bf8a90694d03d2e17f3ddd5536b8775923c3154
Merged-In: I59a95fd8dc12fa5bfcda7f7824e19330a01a0ca8
tree: afdfd3d5dcc7cf73aeccb4921633fdd7c086c47b
  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.