- slf4j-dev - mailman3.qos.ch

[JIRA] Updates for SLF4J-586: MANIFEST.MF exports a package with a former version number
by slf4j developers list 24 Mar '23

24 Mar '23

SLF4J / SLF4J-586 [Open] MANIFEST.MF exports a package with a former version number ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-586 ============================== 1 comment ------------------------------ Hannes Wellmann on 24/Mar/23 18:53 Exactly, please see also SLFJ4-579 for more background. Summed up, the intention is to allow libraries programmed against the slf4j-1 client api, which only import the package org.sfl4j with a version ranges like (1.x,2), to work with the slf4j-api in version 2 in OSGi runtimes as well. Therefore the slf4j.api bundle exports the package org.slf4j in version {{2.0.x}} and {{{}1.7.36{}}}. This is valid because the API in the org.slf4j package has not been broken from sfl4j-1 to 2 and slf4j is a drop-in replacement for slf4j-1 from the client perspective. Furthermore this allows much faster adoption of slf4j-2 in the OSGi world. Otherwise it would only be possible to update to slf4j-2 after all bundles of an application have been prepared for slf4j-2, which could take some time and could become complicated if libraries decide to require slf4j-2. Due to the nature of slf4j you don't want to slf4j.api bundles in your application. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-586: MANIFEST.MF exports a package with a former version number
by slf4j developers list 24 Mar '23

24 Mar '23

SLF4J / SLF4J-586 [Open] MANIFEST.MF exports a package with a former version number ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-586 ============================== 1 comment ------------------------------ Ceki Gülcü on 24/Mar/23 18:12 [~frederic.fays] Thank you for this report. Is the change causing you trouble? The older version to "exports" directive was added on purpose and is not a mistake. Please see [PR 331|https://github.com/qos-ch/slf4j/pull/331] contributed by [~HannesWell]. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-586: MANIFEST.MF exports a package with a former version number
by slf4j developers list 24 Mar '23

24 Mar '23

SLF4J / SLF4J-586 [Open] MANIFEST.MF exports a package with a former version number ============================== 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/SLF4J-586 ============================== Issue created ------------------------------ Frédéric Fays created this issue on 24/Mar/23 16:45 Summary: MANIFEST.MF exports a package with a former version number Issue Type: Bug Affects Versions: 2.0.7 Assignee: SLF4J developers list Components: Unspecified Created: 24/Mar/23 16:45 Environment: The MANIFEST.MF of slf4j.api, version *2.0.7* exports a package as version *1.7.36* Cf. MANIFEST.MF, line 12 Export-Package: org.slf4j;uses:="org.slf4j.event,org.slf4j.helpers,org.slf4j.spi";version="1.7.36" Please fix the version number to its effective version number, i.e. 2.0.7 (or whatsoever the current new version you are working on) Priority: Minor Reporter: Frédéric Fays ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-578: OSGi: jcl-over-slf4j does not export org.apache.commons.logging.impl
by slf4j developers list 23 Mar '23

23 Mar '23

SLF4J / SLF4J-578 [In Progress] OSGi: jcl-over-slf4j does not export org.apache.commons.logging.impl ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-578 ============================== 1 comment ------------------------------ Dr. Domagoj Ćosić on 23/Mar/23 18:12 I can confirm that it is fixed in 2.0.7 ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-557: MDCCloseable: not a great fit for a try-with-resources statement
by slf4j developers list 23 Mar '23

23 Mar '23

SLF4J / SLF4J-557 [In Progress] MDCCloseable: not a great fit for a try-with-resources statement ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-557 ============================== 1 comment ------------------------------ Alberto Scotto on 23/Mar/23 13:28 To make things more clear. Given the following test: {code:java} @Test public void test() { try (MDC.MDCCloseable ignored = MDC.putCloseable("k", "val")) { log.info("BEGIN try"); throw new RuntimeException(); } catch (Exception e) { log.error("FAILED try", e); // MDC will not be attached to this log at runtime! } }{code} Actual logs produced: {noformat} 2023-03-23 13:21:37,535 INFO MyTest k=val - BEGIN try 2023-03-23 13:21:37,537 ERROR MyTest k= - FAILED try {noformat} Expected: {noformat} 2023-03-23 13:21:37,535 INFO MyTest k=val - BEGIN try 2023-03-23 13:21:37,537 ERROR MyTest k=val - FAILED try{noformat} ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-488: Using slf4j-api-2.0.0-alpha1.jar not possible in OSGi
by slf4j developers list 23 Mar '23

23 Mar '23

SLF4J / SLF4J-488 [Open] Using slf4j-api-2.0.0-alpha1.jar not possible in OSGi ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-488 ============================== 1 comment ------------------------------ Hannes Wellmann on 23/Mar/23 12:18 Looks like a duplicate of SLF4J-457 that is fixed already. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-585: Broken link on website (SimpleLogger)
by slf4j developers list 20 Mar '23

20 Mar '23

SLF4J / SLF4J-585 [Resolved] Broken link on website (SimpleLogger) ============================== Here's what changed in this issue in the last few minutes. There are 2 updates, 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-585 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 20/Mar/23 22:38 Resolution: Fixed Status: Resolved (was: In Progress) ============================== 1 comment ------------------------------ Ceki Gülcü on 20/Mar/23 22:38 [~Cyclone] Thank you for reporting this problem. The issue is now fixed. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-585: Broken link on website (SimpleLogger)
by slf4j developers list 20 Mar '23

20 Mar '23

SLF4J / SLF4J-585 [Open] Broken link on website (SimpleLogger) ============================== 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/SLF4J-585 ============================== Issue created ------------------------------ ILya Chilikin created this issue on 20/Mar/23 20:58 Summary: Broken link on website (SimpleLogger) Issue Type: Bug Affects Versions: 2.0.6 Assignee: SLF4J developers list Created: 20/Mar/23 20:58 Environment: Windows 10 Chrome 110 Labels: documentation Priority: Minor Reporter: ILya Chilikin Description: There is a broken link on web site https://www.slf4j.org/manual.html#swapping In text slf4j-simple-2.0.6.jar Binding/provider for Simple implementation ... "Simple" is a link leading to https://www.slf4j.org/apidocs/org/slf4j/impl/SimpleLogger.html which returns 404 Not Found error. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-579: Export slf4j packages in version 1 and 2 in OSGi-Manifests
by slf4j developers list 17 Mar '23

17 Mar '23

SLF4J / SLF4J-579 [Resolved] Export slf4j packages in version 1 and 2 in OSGi-Manifests ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-579 ============================== 1 comment ------------------------------ Hannes Wellmann on 17/Mar/23 22:23 > After some discussion, it was agreed to export {{slf4j-api}} as both versions 2.0.x and 1.7.x and other packages as version 2.0.x only. I would like to make it more clear that the {{slf4j-api}} bundle (Bundle-SymbolicName: {{{}slf4j.api{}}}) only exports the package {{org.slf4j}} in version 2.0.x and 1.7.x. All of its other packages, which are considered only relevant for logging-backends, are exported in version 2.0.x only. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-584: slf4j-api has no javadocs
by slf4j developers list 17 Mar '23

17 Mar '23

SLF4J / SLF4J-584 [Resolved] slf4j-api has no javadocs ============================== Here's what changed in this issue in the last few minutes. There are 2 updates. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-584 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 17/Mar/23 20:43 Resolution: Fixed Status: Resolved (was: In Progress) ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0