- slf4j-dev - mailman3.qos.ch

[JIRA] (SLF4J-408) Incorrect module name for log4j-over-slf4j
by QOS.CH (JIRA) 22 Apr '17

22 Apr '17

Stephen Colebourne created SLF4J-408: ---------------------------------------- Summary: Incorrect module name for log4j-over-slf4j Key: SLF4J-408 URL: https://jira.qos.ch/browse/SLF4J-408 Project: SLF4J Issue Type: Bug Components: log4j-over-slf4j Affects Versions: 1.8.0-alpha1 Reporter: Stephen Colebourne Assignee: SLF4J developers list I need to write this exact use case up in more detail, but see the comments section of my [naming article|http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html] Basically, the module name must be the same for both the real log4j and the "fake" one being supplied by this artifact. This is because the purpose of this module is to replace the log4j one, and because two packages cannot be in the same module. It is up to the build system, ie. Maven, to select the correct artifact to fulfill a given module name. Based on discussions on the commons-dev mailing list, I'm proposing [these as the module names|http://mail-archives.apache.org/mod_mbox/commons-dev/201704.mbox/%3CC…] notably `org.apache.logging.log4j`. (This is based on my super-package reverse-DNS standard naming approach) Thus the module-info.java file needs to change from a module name of `org.slf4j.log4j_over_slf4j` to `org.apache.logging.log4j`. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-407) Jigsaw modules contain clashing package
by QOS.CH (JIRA) 22 Apr '17

22 Apr '17

Stephen Colebourne created SLF4J-407: ---------------------------------------- Summary: Jigsaw modules contain clashing package Key: SLF4J-407 URL: https://jira.qos.ch/browse/SLF4J-407 Project: SLF4J Issue Type: Bug Components: Implementations Affects Versions: 1.8.0-alpha1 Reporter: Stephen Colebourne Assignee: SLF4J developers list Looking at the slf4j-jdk14 and slf4j-nop artifacts, they both appear to contain the package `org.slf4j.impl`. Jigsaw will refuse to load two modules that contain the same package, so this will be a problem. I know that SLF4J does not intend users to load both of these modules at the same time. But the current setup means that it will be the JPMS runtime that rejects it, meaning that there is no chance for SLF4J to output a helpful message (as I believe it does today). The solution to this would appear to be to move the `org.slf4j.impl` package to `org.slf4j.jul.impl` and `org.slf4j.nop.impl`. As the impl package is not exported, this should not affect any user code (except code that would have been affected anyway). I imagine this affects other slf4j artifacts. I also note that [this module-info.java|https://github.com/qos-ch/slf4j/blob/1_8_0-SNAPSHOT/slf4j-…] exports the `org.slf4j.jul` package, which seems unnecessary (simple and nop do not export their package). See [here|http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html] for more information on naming. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j]
by ceki 13 Apr '17

13 Apr '17

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

1 0

[qos-ch/slf4j] ae16a0: update new and faq
by Ceki Gulcu 13 Apr '17

13 Apr '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: ae16a03219821ec78e8dd456cb3e0c20e5adcda8 https://github.com/qos-ch/slf4j/commit/ae16a03219821ec78e8dd456cb3e0c20e5ad… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-04-13 (Thu, 13 Apr 2017) Changed paths: M slf4j-site/src/site/pages/faq.html M slf4j-site/src/site/pages/news.html Log Message: ----------- update new and faq

1 0

[JIRA] (SLF4J-406) 1.8.0-alpha0 puts unwanted message "*********post initializaiton" on stdout
by QOS.CH (JIRA) 13 Apr '17

13 Apr '17

[ https://jira.qos.ch/browse/SLF4J-406?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü resolved SLF4J-406. ------------------------------ Resolution: Fixed > 1.8.0-alpha0 puts unwanted message "*********post initializaiton" on stdout > --------------------------------------------------------------------------- > > Key: SLF4J-406 > URL: https://jira.qos.ch/browse/SLF4J-406 > Project: SLF4J > Issue Type: Bug > Affects Versions: 1.8.0-alpha0 > Reporter: Jan-Willem van den Broek > Assignee: SLF4J developers list > Fix For: 1.8.0-alpha1 > > > We use slf4j-log4j12. After upgrading from 1.7.25 to 1.8.0-alpha0, we get the message "*********post initializaiton" on standard out. > This broke some of our command line tooling, so we reverted back to 1.7.25. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j] bcb318: fix SLF4J-406
by Ceki Gulcu 13 Apr '17

13 Apr '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: bcb318771cc50d7c8cd0183285f65c7e335e35ed https://github.com/qos-ch/slf4j/commit/bcb318771cc50d7c8cd0183285f65c7e335e… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-04-13 (Thu, 13 Apr 2017) Changed paths: M slf4j-log4j12/src/main/java/org/slf4j/log4j12/Log4jLoggerFactory.java Log Message: ----------- fix SLF4J-406 Commit: 5ece81efcb5c5ad0f23f0be19f46c890c3db4625 https://github.com/qos-ch/slf4j/commit/5ece81efcb5c5ad0f23f0be19f46c890c3db… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-04-13 (Thu, 13 Apr 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-api/pom.xml M slf4j-ext/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: ----------- prepare release 1.8.0-alpha1 Compare: https://github.com/qos-ch/slf4j/compare/248aa303ce22...5ece81efcb5c

1 0

[JIRA] (SLF4J-406) 1.8.0-alpha0 puts unwanted message "*********post initializaiton" on stdout
by QOS.CH (JIRA) 13 Apr '17

13 Apr '17

Jan-Willem van den Broek created SLF4J-406: ---------------------------------------------- Summary: 1.8.0-alpha0 puts unwanted message "*********post initializaiton" on stdout Key: SLF4J-406 URL: https://jira.qos.ch/browse/SLF4J-406 Project: SLF4J Issue Type: Bug Affects Versions: 1.8.0 Reporter: Jan-Willem van den Broek Assignee: SLF4J developers list We use slf4j-log4j12. After upgrading from 1.7.25 to 1.8.0-alpha0, we get the message "*********post initializaiton" on standard out. This broke some of our command line tooling, so we reverted back to 1.7.25. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j] 248aa3: fix typos
by Ceki Gulcu 12 Apr '17

12 Apr '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: 248aa303ce22047a282468c498a455bb2ca8c517 https://github.com/qos-ch/slf4j/commit/248aa303ce22047a282468c498a455bb2ca8… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-04-12 (Wed, 12 Apr 2017) Changed paths: M slf4j-site/src/site/pages/codes.html Log Message: ----------- fix typos

1 0

[JIRA] (SLF4J-371) Support the lambda expression in the Logger
by QOS.CH (JIRA) 12 Apr '17

12 Apr '17

[ https://jira.qos.ch/browse/SLF4J-371?page=com.atlassian.jira.plugin.system.… ] Herman Bovens commented on SLF4J-371: ------------------------------------- Any updates? Log4j2 has this exact feature already since version 2.4 (almost a year ago). > Support the lambda expression in the Logger > ------------------------------------------- > > Key: SLF4J-371 > URL: https://jira.qos.ch/browse/SLF4J-371 > Project: SLF4J > Issue Type: Improvement > Components: Core API > Affects Versions: 1.7.22 > Reporter: MiNG > Assignee: SLF4J developers list > > In some cases, we don't want to calculate the expression for logging eagerly cause the performance reason. Then, we would write the code like the following: > ``` > if (LOGGER.isWarnEnabled()) > { > LOGGER.warn("some message: {}", Json.serialize(obj)); > } > ``` > Before JDK8, there is no way to encapsulate the above code, because the expression is always calculated before passed as an argument. So, many "if"s appear in the code and smell badly. > Now, the lambda expression is supported by JDK8, the above could be simplified like following: > ``` > LOGGER.warn(formatter -> formatter.format("some message: {}", Json.serialize(obj))); > ``` > With the default method definition in the org.slf4j.Logger: > ``` > public interface Logger > { > default void warn(Function<MessageFormatter, String> messageSupplier) > { > if (this.isWarnEnabled()) > { > /* Calculate the expression only if the WARN level logging is enabled. */ > this.warn(messageSupplier.apply(this.getFormatter())); > } > } > } > ``` -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-405) Android app with transitive (unrestricted?) dependencies from slf4j does not compile under Android Studio
by QOS.CH (JIRA) 10 Apr '17

10 Apr '17

[ https://jira.qos.ch/browse/SLF4J-405?page=com.atlassian.jira.plugin.system.… ] Lev commented on SLF4J-405: --------------------------- Yes, I have seen error message about problems with module-info class (it has 53 version but only 52 version is supported now) in logcat... > Android app with transitive (unrestricted?) dependencies from slf4j does not compile under Android Studio > ---------------------------------------------------------------------------------------------------------- > > Key: SLF4J-405 > URL: https://jira.qos.ch/browse/SLF4J-405 > Project: SLF4J > Issue Type: Bug > Components: Core API > Affects Versions: 1.8.0 > Environment: Windows 10 > Android Studio 2.3 > Reporter: Lev > Assignee: SLF4J developers list > > I have a huge Android (Gradle) project which had been compiling just fine till 07.04.2017 (yesterday) under Android Studio 2.3. > Now I have > *Error:Execution failed for task ':app:compileReleaseJavaWithJavac'.* > *> Could not expand ZIP 'C:\Users\1\.gradle\caches\modules-2\files-2.1\org.slf4j\slf4j-api\1.8.0-alpha0\3745fbc3ca51456387cf068d66442513898a42f1\slf4j-api-1.8.0-alpha0.jar'.* > I am not using slf4j-api directly, but I suppose that some of .aar libs included in my project (or Andoid Studio !?) do that and probably on the "unrestricted" basis, i.e. as: > *compile 'org.slf4j:slf4j-api:1.+'* > So, there was no problem before 07.04.2017, but yesterday your have updated your https://www.slf4j.org/dist/ with [slf4j-1.8.0-alpha0|https://www.slf4j.org/dist/slf4j-1.8.0-alpha0.zip] and I have got problems. > Would you be so kind to remove this version from your repo, because I am using Java 8 in my project and therefore I can't restrict himself with using of slf4j-1.7.x by means of gradle command. More over I have no idea which of .aar libraries in my project uses slf4j by inappropriate way. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0