Logback

Java的可靠、通用、快速和灵活的日志框架。(The reliable, generic, fast and flexible logging framework for Java. )

Github星跟蹤圖

Logback旨在作为受欢迎的log4j项目的继承者,它将从log4j离开的地方开始。

Logback的架构是非常通用的,以便在不同的情况下应用。 目前,logback分为三个模块:logback-core,logback-classic和logback-access。

对数核心模块为其他两个模块奠定了基础。 logback-classic模块可以被同化到显着改进的log4j版本。 此外,logback-classic本机实现SLF4J API,以便您可以轻松地在logback和log4j或java.util.logging(JUL)之类的日志记录框架之间来回切换。
回溯访问模块与Servlet容器(如Tomcat和Jetty)集成,以提供HTTP访问日志功能。 请注意,您可以轻松地在logback-core之上构建自己的模块。

主要指標

概覽
名稱與所有者qos-ch/logback
主編程語言Java
編程語言HTML (語言數: 11)
平台
許可證Other
所有者活动
創建於2009-08-20 18:48:24
推送於2025-03-29 17:24:32
最后一次提交2025-03-29 18:24:27
發布數146
最新版本名稱v_1.5.18 (發布於 2025-03-18 14:00:54)
第一版名稱release_0.9.1 (發布於 2009-08-20 20:29:40)
用户参与
星數3.1k
關注者數145
派生數1.3k
提交數4.7k
已啟用問題?
問題數167
打開的問題數103
拉請求數229
打開的拉請求數206
關閉的拉請求數258
项目设置
已啟用Wiki?
已存檔?
是復刻?
已鎖定?
是鏡像?
是私有?

About logback

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.

Building logback

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

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.

Pull requests

If you are interested in improving logback, great! The logback community
looks forward to your contribution. Please follow this process:

  1. 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.

  2. Fork qos-ch/logback. 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.

  4. Please add unit tests for your work if appropriate. It usually is.

  5. 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.

  6. Submit a pull request to logback from from your commit page on
    github.

Build Status

Build Status