- slf4j-dev - mailman3.qos.ch

[JIRA] Updates for SLF4J-541: log4j-over-slf4j MANIFEST.MF has corrupt Export-Package declaration
by QOS.CH (JIRA) 08 Feb '22

08 Feb '22

SLF4J / SLF4J-541 [Open] log4j-over-slf4j MANIFEST.MF has corrupt Export-Package declaration ============================== 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-541 ============================== 1 comment ------------------------------ Ceki Gülcü on 08/Feb/22 8:31 AM This happened when all references to log4j were removed. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-541: log4j-over-slf4j MANIFEST.MF has corrupt Export-Package declaration
by QOS.CH (JIRA) 08 Feb '22

08 Feb '22

SLF4J / SLF4J-541 [Open] log4j-over-slf4j MANIFEST.MF has corrupt Export-Package declaration ============================== 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-541 ============================== Issue created ------------------------------ Flavio Donzé created this issue on 08/Feb/22 7:49 AM Summary: log4j-over-slf4j MANIFEST.MF has corrupt Export-Package declaration Issue Type: Bug Affects Versions: 1.7.33, 1.7.34, 1.7.35 Assignee: SLF4J developers list Components: log4j-over-slf4j Created: 08/Feb/22 7:49 AM Priority: Major Reporter: Flavio Donzé Description: Since Version 1.7.33 until 1.7.35 the MANIFEST.MF contains the Export-Package declaration: {code:java} Export-Package: org.apache.log4j;version=${log4j.version},org.apache.l og4j.helpers;version=${log4j.version},org.apache.log4j.spi;version=${ log4j.version},org.apache.log4j.xml;version=${log4j.version}older {code} The *${log4j.version}* should have been replaced by the actual Version in the bulid-process. In Version 1.7.32 the declaration was: {code:java} Export-Package: org.apache.log4j;version=1.2.17,org.apache.log4j.helpe rs;version=1.2.17,org.apache.log4j.spi;version=1.2.17,org.apache.log4 j.xml;version=1.2.17 {code} Bundles: [https://mvnrepository.com/artifact/org.slf4j/log4j-over-slf4j] ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-526: Idea for fluent API improvement
by QOS.CH (JIRA) 02 Feb '22

02 Feb '22

SLF4J / SLF4J-526 [Open] Idea for fluent API improvement ============================== 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-526 ============================== 1 comment ------------------------------ Adrian Shum on 02/Feb/22 1:07 PM @pedrolamarao Not too familiar with Groovy but if you can slightly enhance atDebug etc in Groovy by setting the delegate of the closure to the builder, it will look even better: {code:java} logger.atDebug { message("....") arg("...") arg("...") } {code} ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-526: Idea for fluent API improvement
by QOS.CH (JIRA) 02 Feb '22

02 Feb '22

SLF4J / SLF4J-526 [Open] Idea for fluent API improvement ============================== 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-526 ============================== 1 comment ------------------------------ Adrian Shum on 02/Feb/22 12:53 PM Hi Ceki, I have raised a new PR to demonstrate the idea of using lambda to set up the logging event. Some slight refactoring on LoggingEventBuilder has been done too to better separate the responsibility of Fluent API and Fluent Builder, which should highly reduce inappropriate method call that you might be in concern, e.g. calling log(...) in the lambda; calling setMessage() (which cause log() be forgotten) during fluent API call. There should be more code cleanup needed (e.g. method name of "makeLoggingEventBuilder()" etc) but you may take a look if this direction is something valuable to proceed and I can help further work on it if you don't mind. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-539: Gradle build fails with SLF4J 1.7.34
by QOS.CH (JIRA) 30 Jan '22

30 Jan '22

SLF4J / SLF4J-539 [Resolved] Gradle build fails with SLF4J 1.7.34 ============================== 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-539 ============================== 1 comment ------------------------------ Alexander Veit on 30/Jan/22 5:40 PM Vladimir, since the newer version 1.7.35 is in the Maven repository you have to replace '1.7.+' with '1.7.34' in the provided build.gradle to reproduce the error. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-540: Backward compatibility problem with 1.7.34 update
by QOS.CH (JIRA) 28 Jan '22

28 Jan '22

SLF4J / SLF4J-540 [Open] Backward compatibility problem with 1.7.34 update ============================== 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-540 ============================== 1 comment ------------------------------ Jeremy Landis on 28/Jan/22 3:16 AM @ceki Sorry it is a bit vague on purpose. All good, got some very useful information here I've passed on. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-540: Backward compatibility problem with 1.7.34 update
by QOS.CH (JIRA) 27 Jan '22

27 Jan '22

SLF4J / SLF4J-540 [Open] Backward compatibility problem with 1.7.34 update ============================== 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-540 ============================== 1 comment ------------------------------ Ceki Gülcü on 27/Jan/22 8:29 PM I seem to be missing a lot of context here. Anyway, glad that things seem to be sorted out? ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-540: Backward compatibility problem with 1.7.34 update
by QOS.CH (JIRA) 27 Jan '22

27 Jan '22

SLF4J / SLF4J-540 [Open] Backward compatibility problem with 1.7.34 update ============================== 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-540 ============================== 1 comment ------------------------------ Jeremy Landis on 27/Jan/22 8:14 PM @vladimirsitnikov thank you for that information. Corporate team not on my team but will report that to respective team as clearly needs fixed in our space. Appreciate you providing that. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-540: Backward compatibility problem with 1.7.34 update
by QOS.CH (JIRA) 27 Jan '22

27 Jan '22

SLF4J / SLF4J-540 [Open] Backward compatibility problem with 1.7.34 update ============================== 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-540 ============================== 1 comment ------------------------------ Vladimir Sitnikov on 27/Jan/22 7:35 PM @hazendaz, I maintain [https://github.com/vlsi/vlsi-release-plugins#license-gather-plugin] and I am surprised you went that far without the tool supporting the fetching the license from "parent pom". That was one of the first cases I had to support due to the very common use of the pattern. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-539: Gradle build fails with SLF4J 1.7.34
by QOS.CH (JIRA) 27 Jan '22

27 Jan '22

SLF4J / SLF4J-539 [Resolved] Gradle build fails with SLF4J 1.7.34 ============================== 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-539 ============================== 1 comment ------------------------------ Vladimir Sitnikov on 27/Jan/22 7:39 PM @Veit, please provide the reproducer. configurations.api.setCanBeResolved(true) should not be used. Prefer Sync task if you absolutely need to copy the jars (which you should rarely need in practice). Prefer runtimeClasspath or testRuntimeClasspath configurations or create your own configuration. api is non-resolvable, and there are good reasons for that. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0