STABLE version (ACTIVELY DEVELOPED)

The current actively developed version of logback-core and logback-classic is 1.5.36. It requires JDK 11 or later and SLF4J version 2.0.1 or later at runtime. It was built with JDK 21 and SLF4J version 2.0.17. It contains few optional components such as SMTPAppender and LogbackServletContextListener which depend on Jakarta EE (jakarta.* namespace).

The 1.5.x series is a direct descendant of and a drop-in replacement for the 1.4.x series. It differs from the 1.4.x series by the relocation of the logback-access module which was moved to its own separate github repository.

Older stale versions (END-OF-LIFE)

• The 1.4.x series for logback-core and logback-classic is no loger actively developed and has reached END-OF-LIFE. Moreover, the 1.5.x is a drop in replacement for the 1.4.x series.

• The 1.3.x series has reached END-OF-LIFE. It requires SLF4J version 2.0.x and JDK 8. It contains few optional components such as SMTPAppender and LogbackServletContextListener which depend on Java EE (javax.* namespace). Please note that the 1.3.x series is no loger actively developed.

• The 1.2.x series for logback-core and logback-classic has been deprecated for several years and is no longer maintained. As such, use of the 1.2.x series is discouraged.

For those using Spring-boot 2.7 or earlier, it is possible to upgrade to a more recent version of logback-classic by setting the org.springframework.boot.logging.LoggingSystem system property to none.

Logback-access

For logback-access please refer to its dedicated page.

Binaries in Maven central

Logback artifacts such as .jar, .sources.jar and javadoc.jar files can be downloaded from Maven central under the ch.qos.logback groupId.

Verifying contents

Since early 2022, all logback binaries are reproducible. To verify fidelity to the source code, check out the source code from github with the tag corresponding to the version you wish to verify. Build and compare.

All logback artifacts published on Maven central are signed. For each artifact, there is an associated signature file with the .asc suffix. See SECURITY.md for detailed instructions.