- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1705) Upgrading logback from 1.2.6 to 1.3.0 stops logging
by QOS.CH (JIRA) 13 Nov '22

13 Nov '22

1 0

[JIRA] Updates for LOGBACK-1705: Upgrading logback from 1.2.6 to 1.3.0 stops logging
by QOS.CH (JIRA) 11 Nov '22

11 Nov '22

logback / LOGBACK-1705 [Open] Upgrading logback from 1.2.6 to 1.3.0 stops logging ============================== 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-1705 ============================== Issue created ------------------------------ SHUBHAM GOSWAMI created this issue on 11/Nov/22 1:04 PM Summary: Upgrading logback from 1.2.6 to 1.3.0 stops logging Issue Type: Bug Affects Versions: 1.3.0 Assignee: Logback dev list Components: logback-classic Created: 11/Nov/22 1:04 PM Environment: In my web application Labels: logging Priority: Blocker Reporter: SHUBHAM Description: I am using 1.3.0 logback-classic version, my application stops logging. The logback.xml file maybe isn't even loaded (if I insert invalid xml or delete it, I get no errors). It works fine with logback 1.2.6. This works: logback-classic-1.2.6.jar + logback-core-1.2.6.jar + slf4j-api-1.7.36.jar This doesn't work: logback-classic-1.3.0.jar + logback-core-1.3.0.jar + slf4j-api-2.0.0.jar ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

New module/functionality for Native Image
by Dmitry Kubakhov 10 Nov '22

10 Nov '22

Hello logback team, My name is Dmitry. In our development process, we are using java, micronaut, and logback for logging. Right now we are planning to move to GraalVM, reactor, and use native-image. The current implementation of the AsyncAppender and RollingFileAppender has issues with native image - Logback Jira <https://jira.qos.ch/browse/LOGBACK-1550>. To fix this problem we are using modified AsyncAppender and RollingFileAppender for native image. We would like to share these changes, but we do not know the best way to do it. This native module from our point of view should not be in the main repository of the logback. There are 2 additional repositories - logback-extensions <https://github.com/qos-ch/logback-extensions> and logback-contrib <https://github.com/qos-ch/logback-contrib> - but they are not maintained anymore. At least, the last releases were in 2018. Please, can you share your thoughts on this? How we can bring these changes to the logback users/developers? Thank you in advance, Dmitry Kubakhov Senior Software Developer

1 0

[JIRA] Updates for LOGBACK-1704: Unchecked definition in LogbackMDCAdapter breaking custom adapters
by QOS.CH (JIRA) 07 Nov '22

07 Nov '22

logback / LOGBACK-1704 [Open] Unchecked definition in LogbackMDCAdapter breaking custom adapters ============================== 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-1704 ============================== Issue created ------------------------------ Alessandro Zoffoli created this issue on 07/Nov/22 3:35 PM Summary: Unchecked definition in LogbackMDCAdapter breaking custom adapters Issue Type: Bug Affects Versions: 1.4.2, 1.4.3, 1.4.4 Assignee: Logback dev list Components: logback-classic Created: 07/Nov/22 3:35 PM Priority: Major Reporter: Alessandro Zoffoli Description: Hi, Starting with 1.4.2 I spotted an issue when defining a custom `LogbackMDCAdapter`. In short, this change [https://github.com/qos-ch/logback/commit/7e3e2ae770c19724b0714c7f48fd33bbc6…] changed the definition of the `setContextMap` to be unchecked (`Map` vs. `Map<String, String>`). This is breaking custom adapters in Scala. I setup a minimal repro here: [https://github.com/AL333Z/logback-issue/blob/main/src/main/scala/MyLogbackA…] Restoring the definition to be `public void setContextMap(Map<String, String> contextMap)` should restore the functionality. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1516) Replace JavaEE dependencies with Jakarta EE
by QOS.CH (JIRA) 02 Nov '22

02 Nov '22

1 0

[JIRA] (LOGBACK-1703) Missing 'exports' statements in module-info.java of logback-core and logback-classic
by QOS.CH (JIRA) 29 Oct '22

29 Oct '22

1 0

[JIRA] Updates for LOGBACK-1703: Missing 'exports ch.qos.logback.classic.model; ' in logback-classic/module-info.java
by QOS.CH (JIRA) 29 Oct '22

29 Oct '22

logback / LOGBACK-1703 [Open] Missing 'exports ch.qos.logback.classic.model;' in logback-classic/module-info.java ============================== Here's what changed in this issue in the last few minutes. This issue has been created View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1703 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 29/Oct/22 5:16 PM Summary: Missing 'exports ch.qos.logback.classic.model;' in logback-classic/module-info.java Issue Type: Bug Affects Versions: 1.3.4, 1.4.4 Assignee: Ceki Gülcü Components: logback-classic Created: 29/Oct/22 5:16 PM Fix Versions: 1.3.5, 1.4.5 Priority: Major Reporter: Ceki Gülcü ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LBAUDIT-6) Logback documentation not tied to releases
by QOS.CH (JIRA) 27 Oct '22

27 Oct '22

1 0

[JIRA] (LOGBACK-1702) Why do we need to judege the size of the list
by QOS.CH (JIRA) 22 Oct '22

22 Oct '22

1 0

[JIRA] (LOGBACK-1702) Why do we need to judege the size of the list
by QOS.CH (JIRA) 22 Oct '22

22 Oct '22

1 0