- slf4j-dev - mailman3.qos.ch

[qos-ch/slf4j] ed9b37: ongoing work
by Ceki Gulcu 20 Mar '17

20 Mar '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: ed9b3712a03cb3e6617745616b9afb0a6c646a85 https://github.com/qos-ch/slf4j/commit/ed9b3712a03cb3e6617745616b9afb0a6c64… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-03-20 (Mon, 20 Mar 2017) Changed paths: M integration/pom.xml M jcl-over-slf4j/pom.xml M jul-to-slf4j/pom.xml M log4j-over-slf4j/pom.xml M osgi-over-slf4j/pom.xml M pom.xml M slf4j-android/pom.xml M slf4j-api/pom.xml M slf4j-api/src/main/java/org/slf4j/LoggerFactory.java R slf4j-api/src/main/java/org/slf4j/impl/StaticLoggerBinder.java A slf4j-api/src/main/java/org/slf4j/spi/SLF4JServiceProvider.java M slf4j-ext/pom.xml M slf4j-jcl/pom.xml M slf4j-jdk14/pom.xml M slf4j-log4j12/pom.xml M slf4j-migrator/pom.xml M slf4j-nop/pom.xml M slf4j-simple/pom.xml M slf4j-site/pom.xml Log Message: ----------- ongoing work

1 0

[JIRA] (SLF4J-401) Upgrade SLF4J binding mechanism to use java.util.ServiceLoader
by QOS.CH (JIRA) 20 Mar '17

20 Mar '17

[ https://jira.qos.ch/browse/SLF4J-401?page=com.atlassian.jira.plugin.system.… ] Patrick Reinhart commented on SLF4J-401: ---------------------------------------- Any contribution to this appreciated? > Upgrade SLF4J binding mechanism to use java.util.ServiceLoader > -------------------------------------------------------------- > > Key: SLF4J-401 > URL: https://jira.qos.ch/browse/SLF4J-401 > Project: SLF4J > Issue Type: Sub-task > Components: Core API > Reporter: Ceki Gülcü > Assignee: Ceki Gülcü > Priority: Blocker > Labels: binding > Fix For: 1.8.0 > > > The {{org.slf4j.impl.StaticXYZBinder}} approach has been surprisingly successful for such a crude mechanism. However, with the advent of Java 9/jigsaw/modularisation we need a more standard approach. {{java.util.ServiceLoader}} introduced in Java 6 seems to fit the bill. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-402) Jigsaw module declerations
by QOS.CH (JIRA) 20 Mar '17

20 Mar '17

Ceki Gülcü created SLF4J-402: -------------------------------- Summary: Jigsaw module declerations Key: SLF4J-402 URL: https://jira.qos.ch/browse/SLF4J-402 Project: SLF4J Issue Type: Sub-task Reporter: Ceki Gülcü Assignee: SLF4J developers list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-401) Upgrade SLF4J binding mechanism to use java.util.ServiceLoader
by QOS.CH (JIRA) 20 Mar '17

20 Mar '17

Ceki Gülcü created SLF4J-401: -------------------------------- Summary: Upgrade SLF4J binding mechanism to use java.util.ServiceLoader Key: SLF4J-401 URL: https://jira.qos.ch/browse/SLF4J-401 Project: SLF4J Issue Type: Improvement Components: Core API Reporter: Ceki Gülcü Assignee: Ceki Gülcü Priority: Blocker Fix For: 1.8.0 The {{org.slf4j.impl.StaticXYZBinder}} approach has been surprisingly successful fro such a crude mechanism. However, with the advent of Java 9/jigsaw/modularisation we need a more standard mechanism. {{java.util.ServiceLoader}} introduced in Java 6 seems to fit the bill. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-154) Copy & paste of LoggerFactory.getLogger
by QOS.CH (JIRA) 19 Mar '17

19 Mar '17

[ https://jira.qos.ch/browse/SLF4J-154?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü commented on SLF4J-154: ---------------------------------- Thank you for the pointer [~sdavids]. I've updated the docs. > Copy & paste of LoggerFactory.getLogger > --------------------------------------- > > Key: SLF4J-154 > URL: https://jira.qos.ch/browse/SLF4J-154 > Project: SLF4J > Issue Type: Bug > Components: Core API > Environment: Operating System: All > Platform: All > Reporter: Thomas Mueller > Assignee: SLF4J developers list > Attachments: clipboard.png > > > This is a feature request. > Currently, when I create a new logger in a class, I copy & paste the following line from another class: > private static Logger log = LoggerFactory.getLogger(AcmeImpl.class); > Sometimes I forget to change the class name. SLF4J could help me here. I suggest to add a new method, so the class name is not required, so that I can copy & paste the line without having to remember that I have to change the class name. Also, it's a bit shorter: > private static Logger log = LoggerFactory.getCallerClassLogger(); > This is copy & paste friendly. The implementation is tricky, but trivial once you understand it: > getCallerClassLogger() { > return getLogger(new Error().getStackTrace()[1].getClassName()); > } > There is a project that tries to solve the copy & paste problem: http://code.google.com/p/morbok/ -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j] 1232e8: document MethodHandles.lookup() pattern
by Ceki Gulcu 19 Mar '17

19 Mar '17

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 1232e8529f5844e03e4d528a88185413761853e2 https://github.com/qos-ch/slf4j/commit/1232e8529f5844e03e4d528a881854137618… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-03-19 (Sun, 19 Mar 2017) Changed paths: M slf4j-site/src/site/pages/faq.html Log Message: ----------- document MethodHandles.lookup() pattern

1 0

[JIRA] (SLF4J-154) Copy & paste of LoggerFactory.getLogger
by QOS.CH (JIRA) 19 Mar '17

19 Mar '17

[ https://jira.qos.ch/browse/SLF4J-154?page=com.atlassian.jira.plugin.system.… ] Sebastian Davids commented on SLF4J-154: ---------------------------------------- Java 7+ one can use the following idiom: {code:java} (static) final Logger logger = LoggerFactory.getLogger(java.lang.invoke.MethodHandles.lookup().lookupClass()); {code} Maybe the documentation could be updated: https://www.slf4j.org/faq.html#declaration_pattern > Copy & paste of LoggerFactory.getLogger > --------------------------------------- > > Key: SLF4J-154 > URL: https://jira.qos.ch/browse/SLF4J-154 > Project: SLF4J > Issue Type: Bug > Components: Core API > Environment: Operating System: All > Platform: All > Reporter: Thomas Mueller > Assignee: SLF4J developers list > Attachments: clipboard.png > > > This is a feature request. > Currently, when I create a new logger in a class, I copy & paste the following line from another class: > private static Logger log = LoggerFactory.getLogger(AcmeImpl.class); > Sometimes I forget to change the class name. SLF4J could help me here. I suggest to add a new method, so the class name is not required, so that I can copy & paste the line without having to remember that I have to change the class name. Also, it's a bit shorter: > private static Logger log = LoggerFactory.getCallerClassLogger(); > This is copy & paste friendly. The implementation is tricky, but trivial once you understand it: > getCallerClassLogger() { > return getLogger(new Error().getStackTrace()[1].getClassName()); > } > There is a project that tries to solve the copy & paste problem: http://code.google.com/p/morbok/ -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-400) Guard exception that can occur when converting a message to a string
by QOS.CH (JIRA) 17 Mar '17

17 Mar '17

Ken Kwon created SLF4J-400: ------------------------------ Summary: Guard exception that can occur when converting a message to a string Key: SLF4J-400 URL: https://jira.qos.ch/browse/SLF4J-400 Project: SLF4J Issue Type: Improvement Components: log4j-over-slf4j Affects Versions: 1.7.25 Environment: * OS : any * JDK : 1.8 (or any) Reporter: Ken Kwon Assignee: SLF4J developers list Attachments: Sample1.zip An exception may occur when converting a message to a string([log4j-over-slf4j/src/main/java/org/apache/log4j/Category.convertToString method|https://github.com/qos-ch/slf4j/blob/master/log4j-over-slf4j/src/mai…] For example, someone implements message class's toString method incorrect. Reprodution steps are described as sample project. Download the project and run command in your console(or IDE) 'mvn clean test', then you can see the test case is failed. I think it is better to ignore the exception and let the Category(Logger) continue to run - for example, if the exception is occured , then slf4j prints the exception and continues to call appenders with null message object. As an idea to resolve this problem, I've modified the slf4j's Category.java code and pull-requested to your slf4j repo([https://github.com/qos-ch/slf4j/pull/175|https://github.com/qos-ch/sl…. Could you comment on this issue? -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j] c7d479: start 1.7.26-SNAPSHOT
by Ceki Gulcu 16 Mar '17

16 Mar '17

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: c7d479e43f17f02693f095f4063b61d4163ac2e2 https://github.com/qos-ch/slf4j/commit/c7d479e43f17f02693f095f4063b61d4163a… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-03-16 (Thu, 16 Mar 2017) Changed paths: M integration/pom.xml M jcl-over-slf4j/pom.xml M jul-to-slf4j/pom.xml M log4j-over-slf4j/pom.xml M osgi-over-slf4j/pom.xml M pom.xml M slf4j-android/pom.xml M slf4j-api/pom.xml M slf4j-ext/pom.xml M slf4j-jcl/pom.xml M slf4j-jdk14/pom.xml M slf4j-log4j12/pom.xml M slf4j-migrator/pom.xml M slf4j-nop/pom.xml M slf4j-simple/pom.xml M slf4j-site/pom.xml Log Message: ----------- start 1.7.26-SNAPSHOT

1 0

[qos-ch/slf4j]
by ceki 16 Mar '17

16 Mar '17

Branch: refs/tags/v_1.7.25 Home: https://github.com/qos-ch/slf4j

1 0