Google Git
Sign in
android / platform / external / slf4j / 5daad1875b1c2a36312e203ebf81666054129c68
commit5daad1875b1c2a36312e203ebf81666054129c68[log] [tgz]
authorColin Cross <[email protected]>Fri Feb 24 20:05:27 2017 -0800
committerColin Cross <[email protected]>Fri Feb 24 20:05:27 2017 -0800
treeb343e96440fcd9d36c3216440d32c9cbee176c09
parentc396492264f26581652c878b18766880ec7c6f86 [diff]
Convert slf4j-hostdex to a static library

slf4j-hostdex is used with LOCAL_STATIC_JAVA_LIBRARIES by
core-tests-hostdex, so it has to be a
BUILD_HOST_DALVIK_STATIC_JAVA_LIBRARY here.

Test: m -j ANDROID_FORCE_JACK_ENABLED=disabled checkbuild
Change-Id: Ib67a13647a1fc8ff3f5bfdfb9bed31fd7994b46a
1 file changed
tree: b343e96440fcd9d36c3216440d32c9cbee176c09
  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.mk
  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.