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

[JIRA] Updates for SLF4J-579: Export slf4j packages in version 1 and 2 in OSGi-Manifests
by QOS.CH (JIRA) 14 Mar '23

14 Mar '23

SLF4J / SLF4J-579 [Open] Export slf4j packages in version 1 and 2 in OSGi-Manifests ============================== 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-579 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 14/Mar/23 11:17 AM Summary: Export slf4j packages in version 1 and 2 in OSGi-Manifests Issue Type: Bug Assignee: SLF4J developers list Created: 14/Mar/23 11:17 AM Priority: Major Reporter: Ceki Gülcü Description: Components: Core API Created: 14/Dec/22 11:11 PM Environment: The documentation claims that SLF4J-2 is binary compatible to slf4j-1, from a client perspective: * [https://www.slf4j.org/faq.html#compatibility] * [https://www.slf4j.org/faq.html#changesInVersion200] In order to ease migration to slf4j-2 in the OSGi world and to allow the usage of libraries that are build against slf4j-1 and therefore have a Import-Package version range with exclusive upper-bound of 2 in an OSGi runtime that has SLF4J-2 installed it would be beneficial if slf4j-api would export its packages in version 1 (probably the latest one) and two. Eventually the Manifest of slf4j-api would have an entry like the following (plus uses-constraints): {code:java} Export-Package: org.slf4j;version="1.7.36", org.slf4j;version="2.0.7", org.slf4j.event;version="1.7.36", org.slf4j.event;version="2.0.7", org.slf4j.helpers;version="1.7.36", org.slf4j.helpers;version="2.0.7" org.slf4j.spi;version="1.7.36", org.slf4j.spi;version="2.0.7" {code} ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-578: Restore full binary compatibility and add baseline-tooling to enforce it in the future
by QOS.CH (JIRA) 14 Mar '23

14 Mar '23

SLF4J / SLF4J-578 [Open] Restore full binary compatibility and add baseline-tooling to enforce it in the future ============================== Here's what changed in this issue in the last few minutes. This issue has been created There are 2 comments. This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-578 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 14/Mar/23 11:09 AM Summary: Restore full binary compatibility and add baseline-tooling to enforce it in the future Issue Type: Bug Assignee: SLF4J developers list Created: 14/Mar/23 11:09 AM Priority: Major Reporter: Ceki Gülcü Description: Reporter: Hannes Wellmann The documentation claims that SLF4-2 is binary compatible to slf4j-1, from a client perspective: * [https://www.slf4j.org/faq.html#compatibility] * [https://www.slf4j.org/faq.html#changesInVersion200] But for example [LoggingEvent.getMarker() in [slf4j-1.7|https://github.com/qos-ch/slf4j/blob/e9ee55cca93c2bf26f14482a9bdf…] was changed to [LoggingEvent.getMarkers() in slf4j-2|https://github.com/qos-ch/slf4j/blob/f85104040ce44ac545e15e4f41ef77…] and now returns a List of Markers instead of a single Marker. This looks like a binary incompatible change to me. Would it be possible to restore the old {{getMarker()}} method as deprecated, in order to restore the binary compatibility? If you are interested, to avoid such changes in the future the [bnd-baseline-maven-plugin could help to avoid such change. |https://github.com/bndtools/bnd/tree/master/maven-plugins/bnd-baseline-maven-plugin]But I would have to find out first, if it is possible to perform the check like if the major version was not increment and thus removals are forbidden. Maybe this will also find other binary incompatible changes. ============================== 2 comments ------------------------------ Ceki Gülcü on 14/Mar/23 11:13 AM Ceki Gülcü on 15/Dec/22 8:33 PM [~HannesWell] In version 1.7, LoggingEvent was used internally and in 2.0.0 it is intended for use by implementations via the fluent API. ------------------------------ Ceki Gülcü on 14/Mar/23 11:14 AM Hannes Wellmann on 16/Dec/22 3:05 PM Thanks for the clearification and the false alarm. Nevertheless are you interested in having some tooling support in the build to ensure binary compatibility? ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-577: Export slf4j packages in version 1 and 2 in OSGi-Manifests
by QOS.CH (JIRA) 14 Mar '23

14 Mar '23

SLF4J / SLF4J-577 [Open] Export slf4j packages in version 1 and 2 in OSGi-Manifests ============================== 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-577 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 14/Mar/23 11:06 AM Summary: Export slf4j packages in version 1 and 2 in OSGi-Manifests Issue Type: Bug Assignee: SLF4J developers list Created: 14/Mar/23 11:05 AM Environment: Priority: Major Reporter: Ceki Gülcü Description: Hannes Wellmann on 16/Dec/22 3:24 PM Issue https://jira.qos.ch/browse/SLF4J-577 turned out to be a false alarm. However this made me think about this issue a bit more and actually only the packages that are relevant for clients should be exported in a version 1.x. The package-info for {{org.slf4j.spi}} states that this package should not be used by clients. @ceki can you clarify if anything from {{org.slf4j.helpers}} respectivly {{org.slf4j.event}} were relevant for clients in{{ SLF4J-1?}} If there is nothing it should not be necessary they should not be exported in version 1 as well. This would also solve the problem that a SLF4J-1 binding would have been wired to the slf4j-api in version 2, but if they e.g. import {{org.slf4j.spi}} in version 1 it can only be wired to slf4j-api in version 1. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-576: Mailman hits bug when trying to subscribe to slf4j-user mailing list
by QOS.CH (JIRA) 14 Mar '23

14 Mar '23

SLF4J / SLF4J-576 Mailman hits bug when trying to subscribe to slf4j-user mailing list ============================== Here's what changed in this issue in the last few minutes. This issue has been deleted ============================== Issue deleted ------------------------------ Ceki Gülcü has deleted this issue on 14/Mar/23 11:04 AM ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-576: Mailman hits bug when trying to subscribe to slf4j-user mailing list
by QOS.CH (JIRA) 13 Mar '23

13 Mar '23

SLF4J / SLF4J-576 [Closed] Mailman hits bug when trying to subscribe to slf4j-user mailing list ============================== 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-576 ============================== 1 comment ------------------------------ Sebastian Kürten on 13/Mar/23 4:52 PM Thanks! ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-576: Mailman hits bug when trying to subscribe to slf4j-user mailing list
by QOS.CH (JIRA) 13 Mar '23

13 Mar '23

SLF4J / SLF4J-576 [Resolved] Mailman hits bug when trying to subscribe to slf4j-user mailing list ============================== 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-576 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 13/Mar/23 3:49 PM Resolution: Fixed Status: Resolved (was: Open) ============================== 1 comment ------------------------------ Ceki Gülcü on 13/Mar/23 3:49 PM [~sebkur] Thank you for this report. This issue has been solved now. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-576: Mailman hits bug when trying to subscribe to slf4j-user mailing list
by QOS.CH (JIRA) 13 Mar '23

13 Mar '23

SLF4J / SLF4J-576 [Open] Mailman hits bug when trying to subscribe to slf4j-user mailing list ============================== Here's what changed in this issue in the last few minutes. This issue has been created There is 1 comment. This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-576 ============================== Issue created ------------------------------ Sebastian Kürten created this issue on 13/Mar/23 3:33 PM Summary: Mailman hits bug when trying to subscribe to slf4j-user mailing list Issue Type: Bug Assignee: SLF4J developers list Components: Unspecified Created: 13/Mar/23 3:33 PM Priority: Major Reporter: Sebastian Kürten Description: I'm trying to sign up here: [https://mailman.qos.ch/mailman/listinfo/slf4j-user] and am getting this error message: h2. Bug in Mailman version 2.1.20 h3. We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. ============================== 1 comment ------------------------------ Sebastian Kürten on 13/Mar/23 3:34 PM I realize this is not an issue with the source code or anything, but it's still related to the project, so it seemed reasonable to report it here. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0