- slf4j-dev - mailman3.qos.ch

[JIRA] Updates for SLF4J-545: lf4j-jdk-platform-logging - SLF4JPlatformLogger should use java.text.MessageFormat - not String.format()
by QOS.CH (JIRA) 18 Mar '22

18 Mar '22

SLF4J / SLF4J-545 [Open] lf4j-jdk-platform-logging - SLF4JPlatformLogger should use java.text.MessageFormat - not String.format() ============================== 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-545 ============================== Issue created ------------------------------ robin created this issue on 18/Mar/22 5:39 AM Summary: lf4j-jdk-platform-logging - SLF4JPlatformLogger should use java.text.MessageFormat - not String.format() Issue Type: Bug Assignee: SLF4J developers list Created: 18/Mar/22 5:39 AM Environment: Component: slf4j-jdk-platform-logging Priority: Major Reporter: robin Description: This line here: [https://github.com/qos-ch/slf4j/blob/master/slf4j-jdk-platform-logging/src/…] {{message = String.format(message, params);}} Should instead be: {{message = MessageFormat.format(message, params);}} Such that is matches the expected format of System.Logger.log() ... as per https://docs.oracle.com/javase/9/docs/api/java/lang/System.Logger.html#log-… ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-511: DefaultLogEventBuilder causes incorrect location information to be logged
by QOS.CH (JIRA) 17 Mar '22

17 Mar '22

SLF4J / SLF4J-511 [Reopened] DefaultLogEventBuilder causes incorrect location information to be logged ============================== 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-511 ============================== 1 comment ------------------------------ Ceki Gülcü on 17/Mar/22 8:50 PM [~rgoers(a)apache.org] Please let me know if 2.0.0-alpha7 fixes the issue. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-511: DefaultLogEventBuilder causes incorrect location information to be logged
by QOS.CH (JIRA) 09 Mar '22

09 Mar '22

SLF4J / SLF4J-511 [Reopened] DefaultLogEventBuilder causes incorrect location information to be logged ============================== 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-511 ============================== 1 comment ------------------------------ Ceki Gülcü on 09/Mar/22 11:43 PM I forgot to mention the {{CallerBoundaryAware}} interface which {{DefaultLoggingEventBuilder}} implements. {{CallerBoundaryAware}} interface comes with a single method, namely {{setCallerBoundary(String fqcn)}}. The {{DefaultLoggingEvent}} class has a {{setCallerBoundary}} method and more importantly the {{org.sflf4j.event.LoggerEvent}} class includes a {{getCallerBoundary}} method. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-544: LoggerFactory only loads services from context class loader
by QOS.CH (JIRA) 04 Mar '22

04 Mar '22

SLF4J / SLF4J-544 [Open] LoggerFactory only loads services from context class loader ============================== 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-544 ============================== Issue created ------------------------------ Tobias Hotz created this issue on 04/Mar/22 3:25 PM Summary: LoggerFactory only loads services from context class loader Issue Type: Bug Affects Versions: 1.8.0-beta4, 2.0.0-alpha6 Assignee: SLF4J developers list Components: Core API Created: 04/Mar/22 3:25 PM Priority: Minor Reporter: Tobias Hotz Description: SLF4J currently uses services loader to find a implementation to bind (See [https://github.com/ichttt/slf4j/blob/74ccf20fab1a35243ae41c2f56f2167e86afbd…]) This can cause issues with certain module classloading setups where the context classloader does not contain any module that has a slf4j implementation, but the classloader of the LoggerFactory class might be different from the context classloader and contain a module that has a slf4j implementation. My suggestion would be to expand findServiceProviders so it also class ServiceLoader.load with the class loader of LoggerFactory (if it is different from the context classloader) and add this to the list as well. This would not change existing behaviour if an implementation can be found with the context classloader, as slf4j always uses the first entry in the list returned by LoggerFactory.findServiceProviders. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-543: Improve slf4j binding diagram
by QOS.CH (JIRA) 28 Feb '22

28 Feb '22

SLF4J / SLF4J-543 [Open] Improve slf4j binding diagram ============================== Here's what changed in this issue in the last few minutes. This issue has been created View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-543 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 28/Feb/22 9:29 PM Summary: Improve slf4j binding diagram Issue Type: Bug Affects Versions: 2.0.0-alpha6 Assignee: Ceki Gülcü Created: 28/Feb/22 9:29 PM Fix Versions: 2.0.0-alpha7 Priority: Major Reporter: Ceki Gülcü Description: Comment on Binding with a logging framework at deployment time, the diagram. This is not an error, but I find the graphical treatment for "SLF4J binding artifact available in classpath" hard to see. Suggest revising the treatment (make the red border more pronounced, change the background color, etc.). https://www.slf4j.org/images/concrete-bindings.png ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-504: Add methods with Supplier into Logger methods
by QOS.CH (JIRA) 15 Feb '22

15 Feb '22

SLF4J / SLF4J-504 [Resolved] Add methods with Supplier into Logger methods ============================== 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-504 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 15/Feb/22 9:48 PM Resolution: Won't Do Status: Resolved (was: Open) ============================== 1 comment ------------------------------ Ceki Gülcü on 15/Feb/22 9:48 PM With the advent of the fluent API this change will not be added. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-542: Multiple dependencies in loggers are not properly taken into account
by QOS.CH (JIRA) 11 Feb '22

11 Feb '22

SLF4J / SLF4J-542 [Open] Multiple dependencies in loggers are not properly taken into account ============================== 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-542 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 11/Feb/22 10:00 AM Summary: Multiple dependencies in loggers are not properly taken into account Issue Type: Bug Assignee: SLF4J developers list Created: 11/Feb/22 10:00 AM Priority: Major Reporter: Ceki Gülcü Description: When a logger declares multiple appenders one of which is an AsyncAppender, the AsyncAppender is not taken into account properly. ============================== 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 [Resolved] log4j-over-slf4j MANIFEST.MF has corrupt Export-Package declaration ============================== 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-541 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 08/Feb/22 2:47 PM Resolution: Fixed Status: Resolved (was: Open) ============================== 1 comment ------------------------------ Ceki Gülcü on 08/Feb/22 2:45 PM This issue is fixed in co [commit 8825027|https://github.com/qos-ch/slf4j/commit/882502706063b46] ============================== 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. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-541 ============================== 1 comment ------------------------------ Flavio Donzé on 08/Feb/22 9:25 AM The resulting _MANIFEST.MF_ in the _log4j-over-slf4j-1.7.36.jar_ looks good: {code:java} Export-Package: org.apache.log4j;version=1.2.18.5,org.apache.log4j.hel pers;version=1.2.18.5,org.apache.log4j.spi;version=1.2.18.5,org.apach e.log4j.xml;version=1.2.18.5 {code} I get the following error during the build, but maybe I'm doing something wrong? (mvn clean verify): [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary for SLF4J 1.7.36: [INFO] [INFO] SLF4J .............................................. SUCCESS [ 0.544 s] [INFO] SLF4J API Module ................................... SUCCESS [ 5.273 s] [INFO] SLF4J Simple Binding ............................... SUCCESS [ 1.952 s] [INFO] SLF4J NOP Binding .................................. SUCCESS [ 1.111 s] [INFO] SLF4J JDK14 Binding ................................ SUCCESS [ 1.646 s] [INFO] SLF4J LOG4J-12 Binding relocated ................... SUCCESS [ 0.008 s] [INFO] SLF4J Reload4j Binding ............................. SUCCESS [ 1.805 s] [INFO] SLF4J JCL Binding .................................. SUCCESS [ 1.063 s] [INFO] SLF4J Android Binding .............................. SUCCESS [ 1.022 s] [INFO] SLF4J Extensions Module ............................ SUCCESS [ 2.813 s] [INFO] JCL 1.2 implemented over SLF4J ..................... SUCCESS [ 1.365 s] [INFO] Log4j Implemented Over SLF4J ....................... SUCCESS [ 1.200 s] [INFO] JUL to SLF4J bridge ................................ SUCCESS [ 1.178 s] [INFO] OSGi LogService implemented over SLF4J ............. SUCCESS [ 0.261 s] [INFO] SLF4J Integration tests ............................ FAILURE [ 5.612 s] [INFO] SLF4J Site ......................................... SKIPPED [INFO] SLF4J Migrator ..................................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 27.231 s [INFO] Finished at: 2022-02-08T09:21:30+01:00 [INFO] ------------------------------------------------------------------------ *[ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.2:run (ant-osgi-test) on project integration: An Ant BuildException has occured: The following error occurred while executing this line:* *[ERROR] D:\temp\log\slf4j\integration\osgi-build.xml:67: Test org.slf4j.test_osgi.BundleTest failed* [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <args> -rf :integration ============================== 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. 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:45 AM [~flavio.donze] Can you please see if [commit 882502|https://github.com/qos-ch/slf4j/commit/882502706063b46] fixes the issue by building from source? The version will be set to 1.2.18.5 ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0