Hello all,
The logback team is happy to announce the release of logback version
1.1.6. It contains important bug fixes and improvements. It should hit
the Maven central repository by the time you read this message.
Here some notable changes that you should be aware of.
* Logback now *requires* SLF4J version 1.7.16 or later.
* MDC values are no longer inherited by child threads.
* Packaging data (as output in stack traces) is now disabled by default.
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
Hello all,
The logback team is happy to announce the release of logback version
1.1.5. It contains bug fixes and improvements. It should hit the
Maven central repository by the time you read this message.
Here some notable changes that you should be aware of.
* Logback now *requires* SLF4J version 1.7.16 or later.
* MDC values are no longer inherited by child threads.
* Packaging data (as output in stack traces) is now disabled by default.
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
Hello all,
The logback team is happy to announce the release of logback version
1.1.4. It contains 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 about this release.
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 Gülcü
Hello all,
I am happy to announce the immediate availability of SLF4J version
1.7.15 which adds the capability to store and replay logging calls
made during initialization. Note that notwithstanding the additional
code for replay, this version remains binary compatible with both the
1.6.x and the 1.7.x series.
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ü
