March 2023 - logback-dev - mailman3.qos.ch

[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 29 Mar '23

29 Mar '23

1 0

[JIRA] (LOGBACK-1711) Deadlock when using Virtual Threads
by logback developers list 27 Mar '23

27 Mar '23

1 0

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

24 Mar '23

1 0

[JIRA] (LOGBACK-1581) logback-access should not use Request.getParameterNames
by logback developers list 23 Mar '23

23 Mar '23

1 0

[JIRA] Updates for LOGBACK-1730: logback-classic exports obsolete/removed package 'org.slf4j.impl' in OSGi runtimes
by logback developers list 23 Mar '23

23 Mar '23

logback / LOGBACK-1730 [Open] logback-classic exports obsolete/removed package 'org.slf4j.impl' in OSGi runtimes ============================== 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-1730 ============================== Issue created ------------------------------ Hannes Wellmann created this issue on 23/Mar/23 17:48 Summary: logback-classic exports obsolete/removed package 'org.slf4j.impl' in OSGi runtimes Issue Type: Bug Affects Versions: 1.3.6, 1.4.6 Assignee: Logback dev list Components: logback-classic Created: 23/Mar/23 17:48 Priority: Minor Reporter: Hannes Wellmann Description: Since SLF4J 2 the connection between SLFJ4 and its providers is established via the Service Loader mechanism, which is enabled in OSGi runtimes using a Service Loader Mediator. The package 'org.slf4j.impl' no longer exists in the logback-classic bundle and therefore can not and need no longer be exported. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

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

23 Mar '23

1 0

[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