ASL 1.1 and ASL 2.0 and BSD and BSD with advertising and GPL+ and GPLv2 and GPLv2 with exceptions and IJG and LGPLv2+ and MIT and MPLv2.0 and Public Domain and W3C and zlib and ISC and FTL and RSA-MD
ASL 1.1 and ASL 2.0 and BSD and BSD with advertising and GPL+ and GPLv2 and GPLv2 with exceptions and IJG and LGPLv2+ and MIT and MPLv2.0 and Public Domain and W3C and zlib
acquired package info from repodata DB: repodata/168fa246962e53d9e0ba8cd4bb51a08b3aef361bac92198bf2677e8950495bf6-primary.sqlite.bz2
The OpenJDK runtime environment 11 without audio and video support.
Logback is intended as a successor to the popular log4j project. Logback's architecture is sufficiently generic so as to apply under different circumstances. At present time, logback is divided into three modules, logback-core, logback-classic and logback-access. The logback-core module lays the groundwork for the other two modules. The logback-classic module can be assimilated to a significantly improved version of log4j. Moreover, logback-classic natively implements the SLF4J API so that you can readily switch back and forth between logback and other logging frameworks such as log4j or java.util.logging (JUL). The logback-access module integrates with Servlet containers, such as Tomcat and Jetty, to provide HTTP-access log functionality. Note that you could easily build your own module on top of logback-core.
The OpenJDK runtime environment 8 without audio and video support.
Logback-access module for Servlet integration
The logback-access module is integrated with servlet containers (such as Tomcat and Jetty) to provide HTTP-access logging capabilities. Note that you can easily build your own modules on top of logback-core.