From announce at qos.ch Fri Jan 20 20:03:06 2017 From: announce at qos.ch (QOS.ch annoucements) Date: Fri, 20 Jan 2017 20:03:06 +0100 Subject: [qos.ch-announce] Release of logback version 1.1.9 Message-ID: Hello all, I am happy to announce the release of logback version 1.1.9. It contains important bug fixes and improvements. It should hit the Maven central repository by the time you read this message. Please refer to the news page for precise details. http://logback.qos.ch/news.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter by following: https://twitter.com/qos_ch Enjoy, -- Ceki From announce at qos.ch Sun Feb 5 15:11:28 2017 From: announce at qos.ch (QOS.ch annoucements) Date: Sun, 5 Feb 2017 15:11:28 +0100 Subject: [qos.ch-announce] Release of logback version 1.1.10 Message-ID: Hello all, I am happy to announce the release of logback version 1.1.10. It contains bug fixes and significant *performance* improvements. It should hit the Maven central repository by the time you read this message. Please refer to the news page for precise details. http://logback.qos.ch/news.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter by following: https://twitter.com/qos_ch Enjoy, -- Ceki From announce at qos.ch Wed Feb 8 23:35:20 2017 From: announce at qos.ch (QOS.ch annoucements) Date: Wed, 8 Feb 2017 23:35:20 +0100 Subject: [qos.ch-announce] Release of logback version 1.2.0 Message-ID: Hello all, I am happy to announce the release of logback version 1.2.0. It contains bug fixes and significant *performance* improvements. It should hit the Maven central repository by the time you read this message. This release also fixes a rather severe serialization vulnerability in SocketServer and ServerSocketReceiver. Users running these components should upgrade immediately. Please refer to the news page for precise details. http://logback.qos.ch/news.html For review of performance figures, see: http://tinyurl.com/logbackPerf You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter by following: https://twitter.com/qos_ch Enjoy, -- Ceki From announce at qos.ch Tue Feb 14 23:45:50 2017 From: announce at qos.ch (QOS.ch annoucements) Date: Tue, 14 Feb 2017 23:45:50 +0100 Subject: [qos.ch-announce] Release of SLF4J version 1.7.23 Message-ID: Hello all, I am happy to announce the immediate availability of SLF4J version 1.7.23, a maintenance release fixing bugs with no new features. It fixes a log4j issue with Java 9. Please refer to the the news page for more details on this release: http://www.slf4j.org/news.html The relevant artifacts should hit the Maven central repository within the next few hours. As of version 1.7.9, SLF4J can automatically detect and report mismatches between the class where a logger is defined and the logger name. This cool feature was contributed by Alexander Dorokhine. I join the undoubtedly many SLF4J users in thanking Alexander for his great work. For more details on this feature see: http://www.slf4j.org/codes.html#loggerNameMismatch The 1.7.x series: The Simple Logging Facade for Java or (SLF4J) serves as a simple facade or abstraction for various logging frameworks, e.g. java.util.logging, log4j and logback, allowing the end user to plug in the desired logging framework at deployment time. The 1.7.x series adds varargs support in Logger methods. Compared to previous versions, 1.7.5 significantly improves logger retrieval times. Users are highly encouraged to migrate to SLF4J 1.7.5 or later. Binary compatibility: Mixing mixing different versions of slf4j-api.jar and SLF4J binding can cause problems. For example, if you are using slf4j-api-1.7.1.jar, then you should also use slf4j-simple-1.7.1.jar, using slf4j-simple-1.5.5.jar will not work. From the client's perspective all versions of slf4j-api are compatible. Client code compiled with slf4j-api-N.jar will run perfectly fine with slf4j-api-M.jar for any N and M. You only need to ensure that the version of your binding matches that of the slf4j-api.jar. You do not have to worry about the version of slf4j-api.jar used to compile a given dependency in your project. You can always use *any* version of slf4j-api.jar, and as long as the version of slf4j-api.jar and its binding match, you should be fine. At initialization time, if SLF4J suspects that there may be an api vs. binding version mismatch problem, it will emit a warning about the suspected mismatch. Version 1.7.x series takes compatibility one step further so that slf4j-api and SLF4J bindings can be freely mixed with artifacts from the 1.6.x or 1.7.x series. In other words, when running under JDK 1.5 or later, version 1.7.x is totally 100% no-ifs-or-buts compatible with the 1.6.x series. Downloading SLF4J: You can download SLF4J, including full source code, class files and documentation on our download page: http://www.slf4j.org/download.html Announcement mailing list: You can receive SLF4J related announcements by subscribing to the SLF4J announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü From announce at qos.ch Thu Mar 16 20:23:11 2017 From: announce at qos.ch (QOS.ch annoucements) Date: Thu, 16 Mar 2017 20:23:11 +0100 Subject: [qos.ch-announce] Release of SLF4J version 1.7.25 Message-ID: Hello all, I am happy to announce the immediate availability of SLF4J version 1.7.25, a maintenance release fixing bugs with no new features. Please refer to the the news page for more details on this release: http://www.slf4j.org/news.html The relevant artifacts should hit the Maven central repository within the next few hours. As of version 1.7.9, SLF4J can automatically detect and report mismatches between the class where a logger is defined and the logger name. This cool feature was contributed by Alexander Dorokhine. I join the undoubtedly many SLF4J users in thanking Alexander for his great work. For more details on this feature see: http://www.slf4j.org/codes.html#loggerNameMismatch The 1.7.x series: The Simple Logging Facade for Java or (SLF4J) serves as a simple facade or abstraction for various logging frameworks, e.g. java.util.logging, log4j and logback, allowing the end user to plug in the desired logging framework at deployment time. The 1.7.x series adds varargs support in Logger methods. Compared to previous versions, 1.7.5 significantly improves logger retrieval times. Users are highly encouraged to migrate to SLF4J 1.7.5 or later. Binary compatibility: Mixing mixing different versions of slf4j-api.jar and SLF4J binding can cause problems. For example, if you are using slf4j-api-1.7.1.jar, then you should also use slf4j-simple-1.7.1.jar, using slf4j-simple-1.5.5.jar will not work. From the client's perspective all versions of slf4j-api are compatible. Client code compiled with slf4j-api-N.jar will run perfectly fine with slf4j-api-M.jar for any N and M. You only need to ensure that the version of your binding matches that of the slf4j-api.jar. You do not have to worry about the version of slf4j-api.jar used to compile a given dependency in your project. You can always use *any* version of slf4j-api.jar, and as long as the version of slf4j-api.jar and its binding match, you should be fine. Downloading SLF4J: You can download SLF4J, including full source code, class files and documentation on our download page: http://www.slf4j.org/download.html Announcement mailing list: You can receive SLF4J related announcements by subscribing to the SLF4J announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü From announce at qos.ch Thu Mar 16 20:27:31 2017 From: announce at qos.ch (QOS.ch annoucements) Date: Thu, 16 Mar 2017 20:27:31 +0100 Subject: [qos.ch-announce] Release of logback version 1.2.2 Message-ID: Hello all, I am happy to announce the release of logback version 1.2.2. It contains bug fixes with no major changes. Note that the 1.2.x series offers significant performance improvements over the 1.1.x series. The 1.2.x series also fixes a rather severe serialization vulnerability in SocketServer and ServerSocketReceiver. Users running these components should upgrade immediately. Please refer to the news page for precise details. http://logback.qos.ch/news.html For review of performance figures, see: http://tinyurl.com/logbackPerf You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter by following: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü From announce at qos.ch Fri Apr 7 12:46:35 2017 From: announce at qos.ch (QOS.ch annoucements) Date: Fri, 7 Apr 2017 12:46:35 +0200 Subject: [qos.ch-announce] Release of SLF4J version 1.8.0-alpha0 Message-ID: Java 9 modularization ===================== I am pleased to announce SLF4J 1.8.0-alpha0, a modularized version of slf4j compatible with Java 9 and in particular its Java Platform Module System (JSR 376), a.k.a project Jigsaw. Although there are no client facing API changes in 1.8.0-alpha0 release, the static binding mechanism has been abandoned in favor of java.util.ServiceLoader introduced in Java 6. It follows that slf4j-api now requires Java 6. Just as importantly, slf4j-api version 1.8.x will no longer search for the StaticLoggerBinder class. Instead of "bindings" now slf4j-api looks for "providers" which ship with slf4j-nop-1.8.x.jar, slf4j-simple-1.8.x.jar or slf4j-jdk14-1.8.x.jar. Given that in some environments, it is not possible to modify the version of slf4j-api, slf4j 1.8.x "providers" also act as 1.7.x/1.6.x "bindings". For example, having slf4j-api-1.8.x.jar and slf4j-simple-1.7.x.jar on the class path will NOT work, whereas having slf4j-api-1.7.x.jar and slf4j-simple-1.8.x.jar on the class path will work fine. In other words: slf4j-api-1.8.x.jar + slf4j-simple-1.7.x.jar ==> "No SLF4J providers found" warning whereas: slf4j-api-1.7.x.jar + slf4j-simple-1.8.x.jar ==> OK Download ======== The relevant artifacts can be obtained via the Maven central repository. OSGi changes ============ While we expect the changes introduced in SLF4J 1.8.x to be rather transparent to users, given JPMS restrictions, implementations had to be moved from the org.slf4.impl package to packages specific to each provider. Consequently, the OSGi declarations in MANIFEST.MF files had to be modified. Our tests indicate that SLF4J version 1.8.x should work fine with OSGi. However, more in depth testing is in order. We are looking for volunteers for such tests. The slf4j-log4j12 module ======================== Due to technical reasons, slf4j-log4j12 could not be modularized in this alpha0 release. However, we expect the problem to be solved in future 1.8.x releases. Announcement mailing list ========================= You can receive SLF4J related announcements by subscribing to the SLF4J announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü From announce at qos.ch Fri Oct 20 15:35:06 2017 From: announce at qos.ch (QOS.ch annoucements) Date: Fri, 20 Oct 2017 15:35:06 +0200 Subject: [qos.ch-announce] Release of SLF4J version 1.8.0-beta0 Message-ID: Java 9 modularization ===================== I am pleased to announce SLF4J 1.8.0-alpha0, a modularized version of slf4j compatible with Java 9 and in particular its Java Platform Module System (JSR 376), a.k.a project Jigsaw. Although there are no client facing API changes in 1.8.0-beta0 release, the static binding mechanism has been abandoned in favor of java.util.ServiceLoader introduced in Java 6. It follows that slf4j-api now requires Java 6. Just as importantly, slf4j-api version 1.8.x will no longer search for the StaticLoggerBinder class. Instead of "bindings" now slf4j-api looks for "providers" which ship with slf4j-nop-1.8.x.jar, slf4j-simple-1.8.x.jar or slf4j-jdk14-1.8.x.jar. Given that having the same package name in different modules is a showstopper in Java 9, the org.slf4j.impl package has been removed from all slf4j modules in slf4j version 1.8.0-beta0. In other words, starting with slf4j 1.8.0-beta0, "providers" will no longer act as 1.7.x/1.6.x "bindings". This is in contrast to 1.8.0-alpha series where providers also acted as bindings. For example, having slf4j-api-1.8.x.jar and slf4j-simple-1.7.x.jar on the class path will NOT work. Moreover, having slf4j-api-1.7.x.jar and slf4j-simple-1.8.x.jar on the class path will NOT work either. The only version combination for slf4j-api+slf4j-simple is version 1.8.x for both artifacts. Download ======== The relevant artifacts can be obtained via the Maven central repository. OSGi changes ============ While we expect the changes introduced in SLF4J 1.8.x to be rather transparent to users, given JPMS restrictions, implementations had to be moved from the org.slf4.impl package to packages specific to each provider. Consequently, the OSGi declarations in MANIFEST.MF files had to be modified. Our tests indicate that SLF4J version 1.8.x should work fine with OSGi. However, more in depth testing is in order. We are looking for volunteers for such tests. The slf4j-log4j12 module ======================== Due to technical reasons, slf4j-log4j12 could not be modularized in this alpha0 release. However, we expect the problem to be solved in future 1.8.x releases. Announcement mailing list ========================= You can receive SLF4J related announcements by subscribing to the SLF4J announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü