- logback-dev - mailman3.qos.ch

[JIRA] Updates for LOGBACK-1672: Unable to set delay in DefaultShutdownHook with logback 1.3.0
by QOS.CH (JIRA) 02 Sep '22

02 Sep '22

logback / LOGBACK-1672 [Open] Unable to set delay in DefaultShutdownHook with logback 1.3.0 ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1672 ============================== Issue created ------------------------------ Juan Pablo Santos Rodríguez created this issue on 02/Sep/22 12:30 PM Summary: Unable to set delay in DefaultShutdownHook with logback 1.3.0 Issue Type: Bug Assignee: Logback dev list Components: logback-core Created: 02/Sep/22 12:30 PM Priority: Major Reporter: Juan Pablo Santos Rodríguez Description: With logback 1.3.0, registering a shutdownHook as {code} ... <shutdownHook class="ch.qos.logback.core.hook.DefaultShutdownHook"> <delay>2000</delay>  </shutdownHook> {code} yields on status manager: {code} 12:24:15,117 |-INFO in ch.qos.logback.core.model.processor.ShutdownHookModelHandler - Registeting shuthown hook with JVM runtime. 12:24:15,121 |-WARN in ch.qos.logback.core.model.processor.ImplicitModelHandler - Ignoring unkown property [delay] in [ch.qos.logback.classic.LoggerContext] {code} with default delay (0) being applied, whereas the (almost) same configuration for logback 1.2.11: {code} ... <shutdownHook class="ch.qos.logback.core.hook.DelayingShutdownHook"> <delay>2000</delay> </shutdownHook> {code} works ok. Small nitpick: note that the class changed name between versions, so migrations to logback 1.3.0 containing that hook have to rename/remove the class attribute on the shutdownHook, thus migration isn't simply replacing jars. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for LOGBACK-1671: ServletContainerInitializer service under wrong package on 1.3.0?
by QOS.CH (JIRA) 01 Sep '22

01 Sep '22

logback / LOGBACK-1671 [Open] ServletContainerInitializer service under wrong package on 1.3.0? ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1671 ============================== Issue created ------------------------------ Chad Wilson created this issue on 01/Sep/22 4:56 PM Summary: ServletContainerInitializer service under wrong package on 1.3.0? Issue Type: Bug Affects Versions: 1.3.0 Assignee: Logback dev list Components: logback-classic Created: 01/Sep/22 4:56 PM Priority: Major Reporter: Chad Wilson Description: I believe that [https://github.com/qos-ch/logback/blob/branch_1.3.x/logback-classic/src/mai…] should be renamed back to {noformat} javax.servlet.ServletContainerInitializer{noformat} on 1.3 after [https://github.com/qos-ch/logback/commit/f1fb809b0bb62c1904f0205dc7472c9500…] and LOGBACK-1666, rather than referring to jakarta.servlet? ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1670) Config files ignored when running with Java modules
by QOS.CH (JIRA) 31 Aug '22

31 Aug '22

1 0

[JIRA] Updates for LOGBACK-1670: Config files ignored when running with Java modules
by QOS.CH (JIRA) 31 Aug '22

31 Aug '22

logback / LOGBACK-1670 [Open] Config files ignored when running with Java modules ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1670 ============================== Issue created ------------------------------ Alexey Gavrilov created this issue on 31/Aug/22 4:47 PM Summary: Config files ignored when running with Java modules Issue Type: Bug Affects Versions: 1.3.0, 1.4.0 Assignee: Logback dev list Components: logback-classic Created: 31/Aug/22 4:47 PM Environment: Java Modules Priority: Critical Reporter: Alexey Gavrilov Description: Logback doesn't load XML configuration files for Java applications running with Java Modules (JPMS). Run 'run.sh' shell script in this repository to reproduce: https://github.com/agavrilov76/logback-jpms-bug The problem is that at startup Logback cannot find 'DefaultJoranConfigurator' (the default implementation of 'ch.qos.logback.classic.spi.Configurator') located inside the 'ch.qos.logback.classic' module. This is because 'ch.qos.logback.classic' doesn't actually declare it provides the implementation. Adding this line to the module's module-info.java can fix the problem: provides ch.qos.logback.classic.spi.Configurator with ch.qos.logback.classic.util.DefaultJoranConfigurator; 'ch.qos.logback.classic.servlet.LogbackServletContainerInitializer' should probably declared the same way ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for LOGBACK-1669: JmxConfigurator no more available in 1.4.0
by QOS.CH (JIRA) 30 Aug '22

30 Aug '22

logback / LOGBACK-1669 [Open] JmxConfigurator no more available in 1.4.0 ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1669 ============================== Issue created ------------------------------ Nicolas Trangosi created this issue on 30/Aug/22 8:55 AM Summary: JmxConfigurator no more available in 1.4.0 Issue Type: Bug Affects Versions: 1.4.0 Assignee: Logback dev list Components: logback-classic Created: 30/Aug/22 8:55 AM Labels: configuration Priority: Major Reporter: Nicolas Trangosi Description: Jmx configurator classes has been removed in commit [fa3de69304h|#diff-8ae0229e7e7fb20672111e24a53db9a86540b5879f84dfb0608b11333d0f06fd] (LOGBACK-1655) thus when logback is starting, the following warn message is displayed: {{17:38:25,712 |-WARN in ch.qos.logback.core.model.processor.ImplicitModelHandler - Ignoring unkown property [jmxConfigurator] in [ch.qos.logback.classic.LoggerContext]}} {{This behaviour change is not described in changelog at https://logback.qos.ch/news.html}} ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

Release of logback versions 1.3.0 and 1.4.0
by Ceki Gülcü 28 Aug '22

28 Aug '22

Hello all, I am thrilled to announce the simultaneous release of logback versions 1.3.0 and 1.4.0. Both versions require slf4j-api version 2.0.0 or later. Given that downstream users are likely to depend on either Java EE (in the javax namespace) or on Jakarta EE (in the jakarta namespace) in their projects, it was deemed important for logback to support both EE alternatives. As such, logback 1.3.x supports Java EE whereas logback 1.4.x supports Jakarta EE, otherwise the two versions are feature identical. Both 1.3.x and 1.4.x series require the fluent-API introduced in SLF4J 2.0.x. The 1.3.x series requires Java 8 at runtime. If you wish to build logback from source, you will need Java 9. Reproducible builds require Java 18. The 1.4.x series requires Java 11 at build time and at runtime. ------------------ Joran, logback's configuration system, has been rewritten to use an internal representation model which can be processed separately. Given the breadth of the changes, support for SiftingAppender was dropped temporarily and reintroduced in logback version 1.3.0-alpha16. Support for Groovy configuration was dropped for security reasons but was recovered by Tucker Pelletier (virtualdogbert). See: https://github.com/virtualdogbert/logback-groovy-config For benchmarking figures please see: http://logback.qos.ch/performance.html Recent logback releases are reproducible. This means that anyone checking out the code corresponding to the release version from github and building that local copy, will get obtain an identical binary to the binary found on Maven central. Note that due to issue MJAR-275 with the module-info.java produced in earlier java versions, reproducible builds require Java 18. Donations and sponsorship You can also support SLF4J/logback/reload4j projects via donations and sponsorship. We thank our current supporters and sponsors for their continued contributions. Sponsorship link: https://github.com/sponsors/qos-ch Announcement mailing list: You can receive SLF4J/logback/reload4j related announcements by subscribing QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce Enjoy, -- Ceki Gülcü

1 0

[JIRA] (LOGBACK-1612) jul LevelChangePropagator is inconsistent with SLF4JBridgeHandler
by QOS.CH (JIRA) 28 Aug '22

28 Aug '22

1 0

[JIRA] (LOGBACK-1612) jul LevelChangePropagator is inconsistent with SLF4JBridgeHandler
by QOS.CH (JIRA) 28 Aug '22

28 Aug '22

1 0

[JIRA] (LOGBACK-1612) jul LevelChangePropagator is inconsistent with SLF4JBridgeHandler
by QOS.CH (JIRA) 27 Aug '22

27 Aug '22

1 0

[JIRA] (LOGBACK-1612) jul LevelChangePropagator is inconsistent with SLF4JBridgeHandler
by QOS.CH (JIRA) 27 Aug '22

27 Aug '22

1 0