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)