October 2022 - logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1701) Rules registered with <newRule> do not trigger
by QOS.CH (JIRA) 20 Oct '22

20 Oct '22

1 0

[JIRA] Updates for LOGBACK-1701: Rules registered with newRule do not trigger
by QOS.CH (JIRA) 20 Oct '22

20 Oct '22

logback / LOGBACK-1701 [Open] Rules registered with newRule do not trigger ============================== 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-1701 ============================== Issue created ------------------------------ Bertrand Renuart created this issue on 20/Oct/22 1:40 PM Summary: Rules registered with newRule do not trigger Issue Type: Bug Affects Versions: 1.3.4, 1.4.4 Assignee: Logback dev list Components: Joran, logback-core Created: 20/Oct/22 1:40 PM Priority: Major Reporter: Bertrand Renuart Description: New rules registered with the <newRule> keyword don't seem to be activated. Example: {code:java} <configuration> <newRule pattern="*/stack" class="...." /> <stack .../> </configuration> {code} This sample configuration produces the following messages when debug is enabled: {code:java} INFO ... NewRuleAction - About to add new Joran parsing rule [*/stack, <classname>]. ... WARN ... ImplicitModelHandler - Ignoring unknown property [stack] in [ch.qos.logback.classic.LoggerContext] {code} After some investigations it happens that the new Action rule is created but not actually registered in the rule store - the code is commented, see [SimpleRuleStore#addRule()|https://github.com/qos-ch/logback/blob/v_1.4.4/lo…] As far as I can tell, the {{SimpleRuleStore}} now expects rules to be registered using a {{Supplier<Action>}} instead of a rule instance. Unfortunately, the {{<newRule>}} action is not updated and keeps registering instances instead of a supplier. This prevents from registering and using custom rules in a Logback XML configuration. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for LOGBACK-1700: check depency declarations in 1.4 and 1.3
by QOS.CH (JIRA) 17 Oct '22

17 Oct '22

logback / LOGBACK-1700 [Open] check depency declarations in 1.4 and 1.3 ============================== 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-1700 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 17/Oct/22 5:14 PM Summary: check depency declarations in 1.4 and 1.3 Issue Type: Sub-task Assignee: Logback dev list Created: 17/Oct/22 5:14 PM Priority: Major Reporter: Ceki Gülcü ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1699) com.sun.mail:javax.mail no longer optional
by QOS.CH (JIRA) 17 Oct '22

17 Oct '22

1 0

[JIRA] (LOGBACK-1699) com.sun.mail:javax.mail no longer optional
by QOS.CH (JIRA) 17 Oct '22

17 Oct '22

1 0

[JIRA] Updates for LOGBACK-1699: com.sun.mail:javax.mail no longer optional
by QOS.CH (JIRA) 17 Oct '22

17 Oct '22

logback / LOGBACK-1699 [Open] com.sun.mail:javax.mail no longer optional ============================== 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-1699 ============================== Issue created ------------------------------ Joe Barnett created this issue on 17/Oct/22 4:23 PM Summary: com.sun.mail:javax.mail no longer optional Issue Type: Bug Affects Versions: 1.3.2 Assignee: Logback dev list Components: logback-classic Created: 17/Oct/22 4:23 PM Priority: Major Reporter: Joe Barnett Description: per LOGBACK-1410, com.sun.mail:javax.mail was optional in logback-classic 1.3.0 and 1.3.1, but the optional qualifier seems to have disappeared since 1.3.2. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for LOGBACK-1698: "Nested appenders are not allowed" warning using SiftingAppender
by QOS.CH (JIRA) 17 Oct '22

17 Oct '22

logback / LOGBACK-1698 [Open] "Nested appenders are not allowed" warning using SiftingAppender ============================== 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-1698 ============================== Issue created ------------------------------ albertus82 created this issue on 17/Oct/22 11:19 AM Summary: "Nested appenders are not allowed" warning using SiftingAppender Issue Type: Bug Affects Versions: 1.4.4 Assignee: Logback dev list Created: 17/Oct/22 11:19 AM Environment: Relevant part of the XML configuration: {code:xml} <appender name="MY_LOG_APPENDER" class="ch.qos.logback.classic.sift.SiftingAppender">  <discriminator> <key>dummy</key> <defaultValue>dummy</defaultValue> </discriminator>  <sift> <appender name="MY_LOG_APPENDER_SIFT" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy"> <fileNamePattern>${logs.directory}/mylog.%d.%i.log</fileNamePattern> <maxFileSize>25MB</maxFileSize> <maxHistory>30</maxHistory> <totalSizeCap>250MB</totalSizeCap> <cleanHistoryOnStart>true</cleanHistoryOnStart> </rollingPolicy> <encoder> <pattern>%d{MMM dd HH:mm:ss} %hostaddr %msg%n</pattern> </encoder> </appender> </sift> </appender> {code} Labels: SiftingAppender Priority: Major Reporter: albertus82 Description: Hi, I'm migrating from 1.2 to 1.4 and I have a {{SiftingAppender}} configured like the example shown in the manual (appender > sift > appender): [https://logback.qos.ch/manual/appenders.html#SiftingAppender] Nevertheless I'm getting the warning "As of logback version 1.3, nested appenders are not allowed", which causes Logback to print its full initalization log. Am I missing something? Thank you. ---- {color:#403294}_Original post: [https://github.com/qos-ch/logback/discussions/604]_{color} ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-267) FixedWindowRollingPolicy performs compression on the logging thread
by QOS.CH (JIRA) 17 Oct '22

17 Oct '22

1 0

[JIRA] (LOGBACK-1695) Modular export missing for ch.qos.logback.core.layout
by QOS.CH (JIRA) 15 Oct '22

15 Oct '22

1 0

[JIRA] (LOGBACK-1610) Jetty 10 support
by QOS.CH (JIRA) 14 Oct '22

14 Oct '22

1 0