Logback旨在作为受欢迎的log4j项目的继承者,它将从log4j离开的地方开始。
Logback的架构是非常通用的,以便在不同的情况下应用。 目前,logback分为三个模块:logback-core,logback-classic和logback-access。
Java的可靠、通用、快速和灵活的日志框架。(The reliable, generic, fast and flexible logging framework for Java. )
Logback旨在作为受欢迎的log4j项目的继承者,它将从log4j离开的地方开始。
Logback的架构是非常通用的,以便在不同的情况下应用。 目前,logback分为三个模块:logback-core,logback-classic和logback-access。
名称与所有者 | qos-ch/logback |
---|---|
主编程语言 | Java |
编程语言 | HTML (语言数: 10) |
平台 | |
许可证 | Other |
发布数 | 132 |
最新版本名称 | v_1.5.6 (发布于 2024-04-17 19:44:03) |
第一版名称 | release_0.9.1 (发布于 2009-08-20 20:29:40) |
创建于 | 2009-08-20 18:48:24 |
推送于 | 2024-04-24 16:46:00 |
最后一次提交 | 2024-04-22 15:27:04 |
星数 | 2.9k |
关注者数 | 151 |
派生数 | 1.2k |
提交数 | 4.5k |
已启用问题? | |
问题数 | 75 |
打开的问题数 | 53 |
拉请求数 | 226 |
打开的拉请求数 | 209 |
关闭的拉请求数 | 235 |
已启用Wiki? | |
已存档? | |
是复刻? | |
已锁定? | |
是镜像? | |
是私有? |
Thank you for your interest in logback, the reliable, generic, fast
and flexible logging library for Java.
The Logback documentation can be found on the project
web-site as well as under
the docs/ folder of the logback distribution.
Version 1.3.x requires Java 9 to compile and build.
More details on building logback is documented at:
https://logback.qos.ch/setup.html#ide
In case of problems please do not hesitate to post an e-mail message
on the logback-user@qos.ch mailing list. However, please do not
directly e-mail logback developers. The answer to your question might
be useful to other users. Moreover, there are many knowledgeable users
on the logback-user mailing lists who can quickly answer your
questions.
If you are interested in improving logback, great! The logback community
looks forward to your contribution. Please follow this process:
Please file a bug
report. Pull requests with
an associated JIRA issue will get more attention.
Optional: Start a discussion on the logback-dev mailing
list about your proposed
change.
Fork qos-ch/logback. Ideally, create a new branch from your fork for
your contribution to make it easier to merge your changes back.
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.
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.
Submit a pull request to logback from from your commit page on
github.