August 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 31 Aug '23

31 Aug '23

SLF4J / SLF4J-579 [Reopened] 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 31/Aug/23 23:12 > I agree marking it as backwards compatible should only be done in case this is automatically checked (e.g. with [https://github.com/bndtools/bnd/tree/master/maven-plugins/bnd-baseline-mave…] and this is kept for all 2.x versions. [~kwin] you could use the bnd-baseline-maven-plugin to check if the org.slf4j.helpers plugin is backwards compatible by using slf4j 1.7.36 as baseline? Nevertheless having tooling to ensure backwards compatibility (or actually correctly applied semantic versioning) would be helpful in case something is overseen. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-592: Mechanism for indicating provider to use for unit tests.
by slf4j developers list 29 Aug '23

29 Aug '23

SLF4J / SLF4J-592 [Resolved] Mechanism for indicating provider to use for unit tests. ============================== 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-592 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 29/Aug/23 14:46 Resolution: Duplicate Status: Resolved (was: Open) ============================== 1 comment ------------------------------ Ceki Gülcü on 29/Aug/23 14:47 Closing as duplicate of SLF4J-450 ============================== 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 25 Aug '23

25 Aug '23

SLF4J / SLF4J-579 [Reopened] 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 ------------------------------ Ceki Gülcü on 25/Aug/23 12:28 [~kwin] I modified the FAQ [entry |https://www.slf4j.org/faq.html#compatibility] to make the language clearer. The entry now specifically mentions the {{org.slf4j}} package. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-437: Create a BOM POM
by slf4j developers list 24 Aug '23

24 Aug '23

SLF4J / SLF4J-437 [Resolved] Create a BOM POM ============================== 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-437 ============================== 1 comment ------------------------------ Ceki Gülcü on 24/Aug/23 22:10 [~garretwilson] Thank you very much for your update. It is highly appreciated. SLF4J uses the maven-deploy-plugin to deploy to Maven Central. I hope to cut an SLF4J release tomorrow and will keep you posted. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-437: Create a BOM POM
by slf4j developers list 23 Aug '23

23 Aug '23

SLF4J / SLF4J-437 [Resolved] Create a BOM POM ============================== 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-437 ============================== 1 comment ------------------------------ Garret Wilson on 23/Aug/23 16:30 Good morning, [~ceki]. I have good news and not-so-good news. It turns out that [m2e-core Issue #1501|https://github.com/eclipse-m2e/m2e-core/issues/1501], in which Eclipse Maven support wasn't correctly resolving dependencies, turned out to be a bug they introduced into the latest development version. It had nothing to do with the BOM POM structure. It only seemed related because that's what I had been changing when I discovered the new dependency calculation bug. (For what it's worth, they just committed a fix for that bug.) The not-so-good is that the [Nexus Staging Maven Plugin|https://github.com/sonatype/nexus-maven-plugins/blob/main/staging/ma…] seems to have a bug that makes it not deploy the top-level POM if another POM is at the same directory level. Thus the structure we were using with the {{parent-pom.xml}} file in the root of the project alongside {{pom.xml}} will cause {{pom.xml}} not to be deployed!!! I filed bug [{{MVNCENTRAL-8292}}|https://issues.sonatype.org/browse/MVNCENTRAL-8292], but I may have to file another ticket for the Nexus Staging Maven Plugin. I don't know the likelihood of it being fixed though; we'll have to see. In the meantime, we'll have to move {{parent-pom.xml}} back into {{parent/pom.xml}}. Don't forget 1) to update the aggregation to say {{<module>parent</module>}}, 2) to remove the {{<relativePath>pom.xml</relativePath>}} inside {{parent/pom.xml}}, and 3) to change the other POMs from {{<relativePath>../parent-pom.xml</relativePath>}} to {{<relativePath>../parent/pom.xml</relativePath>}}. In other words, we'll have to follow the second-to-last structure in my BOM article. I only just now updated [{{MVNCENTRAL-8292}}|https://issues.sonatype.org/browse/MVNCENTRAL-8292] with this latest discovery, so it's possible they could quickly fix this in the Nexus Staging Maven Plugin. In the meantime I'm going to redeploy my {{globalmentor-base}} and {{globalmentor-web}} projects as described in this comment so they wont' be broken. ============================== 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 22 Aug '23

22 Aug '23

SLF4J / SLF4J-579 [Reopened] 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 ------------------------------ Konrad Windszus on 22/Aug/23 16:11 bq. If compatibility was preserved, then that would be the result of luck. Thus, it seems some what dishonest to mark the org.slf4j.helpers package as compatible with both 1.7.x and 2.0.x. This contradicts what is written in https://www.slf4j.org/faq.html#compatibility (which doesn't mention restrictions for certain packages). Can you clarify what you are committing to with regards to backwards-compatibility? I agree marking it as backwards compatible should only be done in case this is automatically checked (e.g. with https://github.com/bndtools/bnd/tree/master/maven-plugins/bnd-baseline-mave…) and this is kept for all 2.x versions. ============================== 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 22 Aug '23

22 Aug '23

SLF4J / SLF4J-579 [Reopened] 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 22/Aug/23 15:46 Resolution: (was: Fixed) Status: Reopened (was: Resolved) ============================== 1 comment ------------------------------ Ceki Gülcü on 22/Aug/23 15:37 [~kwin] Marking org.slf4j.helpers package as compatible bith both 1.7.x and 2.x seems somewhat dishonest. Indeed, actual compatibility would be the result of luck. Moreover, There were a fair amount of classes in the org.slf4j.helpers package that were changed during the development of the 2.x series. If compatibility was preserved, then that would be the result of luck. Thus, it seems some what dishonest to mark the org.slf4j.helpers package as compatible with both 1.7.x and 2.0.x. However, if that is the wish of the OSGi community, then I won't stand in the way. I propose to incorporate the suggested changed but to mark them as "provisional" in case it impacts other users. ============================== 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 Aug '23

17 Aug '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 ------------------------------ Konrad Windszus on 17/Aug/23 11:47 @Ceki Gülcü Do you reconsider the decision to only export org.slf4j.helpers in incompatible version 2.x for SLF4J 2.x? Otherwise making an OSGi bundle using SLF4J will be a lot harder to make compatible both with SLF4J 2.x and 1.x..... ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-437: Create a BOM POM
by slf4j developers list 09 Aug '23

09 Aug '23

SLF4J / SLF4J-437 [Resolved] Create a BOM POM ============================== 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-437 ============================== 1 comment ------------------------------ Garret Wilson on 09/Aug/23 23:50 {quote}This seems to have confused m2e …{quote} After further investigation this may be an m2e bug introduced into a 2.4.x snapshot version; it is not clear if it is related to the POM structure. I'm discussing this with the m2e team and I'll keep you updated. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for SLF4J-599: simplistic migration
by slf4j developers list 09 Aug '23

09 Aug '23

SLF4J / SLF4J-599 [Open] simplistic migration ============================== 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-599 ============================== Issue created ------------------------------ delanym created this issue on 09/Aug/23 22:26 Summary: simplistic migration Issue Type: Bug Affects Versions: 2.0.7 Assignee: SLF4J developers list Components: slf4j-migrator Created: 09/Aug/23 22:26 Priority: Major Reporter: Delany Middleton Description: The migrator seems to be using a string replace methodology, instead of parsing the code and replacing tokens. Kind of frightening. For example {code:java} - headerDisplay.setValue("Service Processor Log Information"); + headerDisplay.setValue("Service Processor Logger Information");{code} ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0