Google Git
Sign in
android / platform / external / slf4j / 373b1ceccea5e41f61f492852762203bb12b69bd
commit373b1ceccea5e41f61f492852762203bb12b69bd[log] [tgz]
authorAlmaz Mingaleev <[email protected]>Tue Dec 14 12:34:43 2021 +0000
committerAlmaz Mingaleev <[email protected]>Tue Dec 14 13:11:04 2021 +0000
tree28bbded431e984b1dca637c17405bba52ae7237e
parentaad5a1c164b55119d5101ef29a5eb8d8fde8b454 [diff]
Limit external/slf4j visibility.

SLF4J is used in mockftpserver only and both of them are used in tests
only.
FTP support probably could be dropped, but in mean time we can
explicitly point out that none of SLF4J or mockftpserver reaches prod
code / env.

Bug: 210532587
Bug: 210594275
Test: atest FtpURLConnectionTest
Change-Id: Ic1257ee5ec44dc093e017ca55fc462666d735892
1 file changed
tree: 28bbded431e984b1dca637c17405bba52ae7237e
  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.