- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1728) Inccorect Bundle-RequiredExecutionEnvironment: JavaSE-1.6
by logback developers list 23 Mar '23

23 Mar '23

1 0

[JIRA] (LOGBACK-1727) Logback: After upgrading to 1.3.6 with SLF4J 2.0.4, logs are being written to unknown.log file.
by logback developers list 23 Mar '23

23 Mar '23

1 0

[JIRA] Updates for LOGBACK-1729: Add OSGi Service Loader Mediator entries to load logback Configurators
by logback developers list 23 Mar '23

23 Mar '23

logback / LOGBACK-1729 [Open] Add OSGi Service Loader Mediator entries to load logback Configurators ============================== 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-1729 ============================== Issue created ------------------------------ Hannes Wellmann created this issue on 23/Mar/23 12:49 Summary: Add OSGi Service Loader Mediator entries to load logback Configurators Issue Type: Improvement Affects Versions: 1.3.5, 1.4.5 Assignee: Logback dev list Components: logback-classic Created: 23/Mar/23 12:49 Environment: The Manifest of logback-classic does not declared the OSGi Service Loader Mediator entries to be able to consume {{logback.classic.spi.Configurator}} services provided by other bundles. At the moment, if one provides a {{Configurator}} in another bundle this has to be workaround. For example when using Apache Aries SPI Fly by using the [Dynamic Weaving by auto properties|[https://aries.apache.org/documentation/modules/spi-fly.html#_dy…] the following VM-argument needs to be added to an application: {{-Dorg.apache.aries.spifly.auto.consumers=ch.qos.logback.classic}} Furthermore the OSGi Service Loader Mediator entry for the provided {{jakarta.servlet.ServletContainerInitializer}} service (implemented by {{{}LogbackServletContainerInitializer{}}}) is missing as well. Priority: Major Reporter: Hannes Wellmann ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for LOGBACK-1728: Inccorect Bundle-RequiredExecutionEnvironment: JavaSE-1.6
by logback developers list 23 Mar '23

23 Mar '23

logback / LOGBACK-1728 [Open] Inccorect Bundle-RequiredExecutionEnvironment: JavaSE-1.6 ============================== 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-1728 ============================== Issue created ------------------------------ Hannes Wellmann created this issue on 23/Mar/23 12:31 Summary: Inccorect Bundle-RequiredExecutionEnvironment: JavaSE-1.6 Issue Type: Bug Affects Versions: 1.3.5, 1.4.5 Assignee: Logback dev list Components: logback-access, logback-classic, logback-core Created: 23/Mar/23 12:31 Environment: The MANIFEST.MF file of logback-core, -classic, and -access contain the OSGi entry {{{}Bundle-RequiredExecutionEnvironment: JavaSE-1.6{}}}, which is outdated since Java-8 is required for logback 1.3 and Java-11 for 1.4. In general the OSGi header {{Bundle-RequiredExecutionEnvironment}} is deprecated and should be replaced by a corresponding osgi.ee required capability. The maven-bundle-plugin can generated all that automatically, if it is not restricted and therefore this issue can simply be solved by removing the {{<_noee>true</_noee>}} and {{<Bundle-RequiredExecutionEnvironment>JavaSE-1.6</Bundle-RequiredExecutionEnvironment> }}configuration elements. Furthermore the maven-bundle-plugin configuration explicitly imports packages that are used in the code and are therefore added any ways. Listing them explicitly could just cause inconsistencies in the future if something changes in this regard. Priority: Major Reporter: Hannes Wellmann ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for LOGBACK-1727: Logback: After upgrading to 1.3.6 with SLF4J 2.0.4, logs are being written to unknown.log file.
by logback developers list 22 Mar '23

22 Mar '23

logback / LOGBACK-1727 [Open] Logback: After upgrading to 1.3.6 with SLF4J 2.0.4, logs are being written to unknown.log file. ============================== 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-1727 ============================== Issue created ------------------------------ Lakshmikanth Reddy created this issue on 22/Mar/23 14:31 Summary: Logback: After upgrading to 1.3.6 with SLF4J 2.0.4, logs are being written to unknown.log file. Issue Type: Bug Affects Versions: 1.3.6 Assignee: Logback dev list Components: logback-core Created: 22/Mar/23 14:31 Labels: siftingAppender Priority: Major Reporter: Lakshmikanth Reddy Description: Hi Team, After upgrading the logback-classic and logback-core to 1.3.6 along with SLF4J to 2.0.4, the logs are being written to unknown.log file. Our config looks exactly like below. {code:java} <configuration> <appender name="SIFT" class="ch.qos.logback.classic.sift.SiftingAppender"> <discriminator class="ch.qos.logback.classic.sift.JNDIBasedContextDiscriminator"> <DefaultValue>unknown</DefaultValue> </discriminator> <sift> <appender name="FILE-${contextName}" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${catalina.base}/logs/${contextName}.log</File> <append>true</append> <immediateFlush>true</immediateFlush> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>${catalina.base}/logs/${contextName}.%i.log.zip</fileNamePattern> <minIndex>1</minIndex> <maxIndex>3</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>20MB</maxFileSize> </triggeringPolicy> <encoder> <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS}|%-5level|${HOSTNAME}|%msg ||%class:%line %xException{full} %n</pattern> </encoder> </appender> </sift> </appender> <root level="INFO"> <appender-ref ref="SIFT" /> </root> </configuration> {code} Our previous version was: logback: 1.2.11 with SLF4J at version 1.7.36. Note: All the required config described in the documentation for JNDI is as is and has not changed. Any pointers to resolve this issue would be great help. Thanks, Lakshmikanth ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] (LOGBACK-1595) Update Jansi library to 2.4.0
by logback developers list 20 Mar '23

20 Mar '23

1 0

[JIRA] (LOGBACK-1713) AppenderFactory not set in SiftingAppender
by logback developers list 16 Mar '23

16 Mar '23

1 0

[JIRA] (LOGBACK-1713) AppenderFactory not set in SiftingAppender
by QOS.CH (JIRA) 15 Mar '23

15 Mar '23

1 0

[JIRA] Updates for LOGBACK-1719: Support for Turbofilters in LoggingEventBuilder
by QOS.CH (JIRA) 14 Mar '23

14 Mar '23

logback / LOGBACK-1719 [Open] Support for Turbofilters in LoggingEventBuilder ============================== 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-1719 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 14/Mar/23 2:03 PM Summary: Support for Turbofilters in LoggingEventBuilder Issue Type: Bug Assignee: Logback dev list Created: 14/Mar/23 2:03 PM Priority: Major Reporter: Ceki Gülcü ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for LOGBACK-1720: Flaky test failure observed
by QOS.CH (JIRA) 14 Mar '23

14 Mar '23

logback / LOGBACK-1720 [Open] Flaky test failure observed ============================== 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-1720 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 14/Mar/23 2:03 PM Summary: Flaky test failure observed Issue Type: Bug Assignee: Logback dev list Created: 14/Mar/23 2:03 PM Priority: Major Reporter: Ceki Gülcü ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0