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

[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 are 2 updates, 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-579 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 17/Mar/23 18:20 Resolution: Fixed Status: Resolved (was: In Progress) ============================== 1 comment ------------------------------ Ceki Gülcü on 17/Mar/23 18: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. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-583: incorrect require-bundle in slf4j-simple to slf4j-api since 2.0.6
by slf4j developers list 17 Mar '23

17 Mar '23

SLF4J / SLF4J-583 [Open] incorrect require-bundle in slf4j-simple to slf4j-api since 2.0.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/SLF4J-583 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 17/Mar/23 8:10 Summary: incorrect require-bundle in slf4j-simple to slf4j-api since 2.0.6 Issue Type: Bug Assignee: SLF4J developers list Created: 17/Mar/23 8:10 Priority: Blocker Reporter: Ceki Gülcü Description: Since 2.0.6 the symbolic names are changed in SLF4J which introduced an inconsistency which creates a problem within OSGi environments slf4j-simple MANIFEST contains this {{}} {code:java} Require-Bundle: slf4j.api {code} while at the same time slf4j-api MANIFEST contains this {{}} {code:java} Bundle-SymbolicName: org.slf4j.api\{code} {{}} *reproduction:* download slf4j-simple and slf4j-api from mvncentral and inspect the manifest in the jars As far as I can tell at this moment it is since the maven-bundle-plugin is used which might be incorrectly configured. It is also weird that there is already a manifest.mf file in the sourcecode which does not seem to be used but overwritten by the maven-bundle-plugin as in manifest.mf files in the source the symbolic bundle names have not changed. Sidenote: all symbolic bundle names have changed which is anyhow a change which results in a lot of work in OSGi based projects as all manifest.mf files need to be adjusted. I have a feeling this was an unwanted change? ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-582: Add license file to Jar
by slf4j developers list 16 Mar '23

16 Mar '23

SLF4J / SLF4J-582 [Open] Add license file to Jar ============================== 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-582 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 16/Mar/23 18:28 Summary: Add license file to Jar Issue Type: Improvement Affects Versions: 2.0.6 Assignee: SLF4J developers list Created: 16/Mar/23 18:28 Fix Versions: 2.0.7 Priority: Major Reporter: Ceki Gülcü Description: Tobias Wittmann created this issue on 25/Jan/23 10:51 AM For a customer project an OpenSource report has to be generated. Therefore a scanner was created to extract the licence information from our dependencies. This scanner can extract all informaton from the Jar file. Therefore it would be great to have the license information included in the Jar file as LICENSE.txt file. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

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

16 Mar '23

SLF4J / SLF4J-580 [Resolved] DUPLICATE: 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 are 2 updates. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-580 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 16/Mar/23 17:58 Resolution: Duplicate Status: Resolved (was: In Progress) ============================== 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 16 Mar '23

16 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 ------------------------------ Ceki Gülcü on 16/Mar/23 17:59 [~domagoj] I can confirm this issue. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-581: Fully automate OSGi metadata creation and fix broken OSGi-metadata in slf4j-api
by slf4j developers list 16 Mar '23

16 Mar '23

SLF4J / SLF4J-581 [Open] Fully automate OSGi metadata creation and fix broken OSGi-metadata in slf4j-api ============================== 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-581 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 16/Mar/23 18:00 Summary: Fully automate OSGi metadata creation and fix broken OSGi-metadata in slf4j-api Issue Type: Improvement Assignee: SLF4J developers list Created: 16/Mar/23 18:00 Priority: Major Reporter: Ceki Gülcü ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-580: OSGi: jcl-over-slf4j does not export org.apache.commons.logging.impl
by QOS.CH (JIRA) 15 Mar '23

15 Mar '23

SLF4J / SLF4J-580 [Open] 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-580 ============================== 1 comment ------------------------------ Ceki Gülcü on 15/Mar/23 20:48 I can confirm this bug. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-577: Restore full binary compatibility and add baseline-tooling
by QOS.CH (JIRA) 15 Mar '23

15 Mar '23

SLF4J / SLF4J-577 [Open] Restore full binary compatibility and add baseline-tooling ============================== Here's what changed in this issue in the last few minutes. There are 2 comments. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-577 ============================== 2 comments ------------------------------ Ceki Gülcü on 15/Mar/23 20:22 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. So, close but no cigar. ------------------------------ Ceki Gülcü on 15/Mar/23 20:23 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-580: OSGi: jcl-over-slf4j does not export org.apache.commons.logging.impl
by QOS.CH (JIRA) 14 Mar '23

14 Mar '23

SLF4J / SLF4J-580 [Open] OSGi: jcl-over-slf4j does not export org.apache.commons.logging.impl ============================== 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-580 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 14/Mar/23 11:40 AM Summary: OSGi: jcl-over-slf4j does not export org.apache.commons.logging.impl Issue Type: Bug Assignee: SLF4J developers list Created: 14/Mar/23 11:40 AM Priority: Major Reporter: Ceki Gülcü Description: Created: 19/Dec/22 4:40 PM Reporter: Dr. Domagoj Ćosić jcl-over-slf4j did export {{org.apache.commons.logging.impl}} in all previous versions. In release 2.0.6, it does not. I cannot imagine that this is a conscious API change. Expected behavior: all contained packages as also exported in {{Export-Package}}. ============================== 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 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. There are 3 comments. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-579 ============================== 3 comments ------------------------------ Ceki Gülcü on 14/Mar/23 11:29 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:29 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? ------------------------------ Ceki Gülcü on 14/Mar/23 11:30 AM Hannes Wellmann on 16/Dec/22 3:24 PM Issue https://jira.qos.ch/browse/SLF4J-578 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