Hello all,
I am pleased to announce SLF4J 2.0.0-alpha5. This release fixes
an issue with Java Platform Logging API (JEP 264) support when
running under the class-path (but not the module-path). JEP 264
support is new in SLF4J 2.0.0-alpha4.
The 2.0.x series introduces a backward-compatible fluent logging
API. By backward-compatible, we mean that existing logging
frameworks do not have to be changed in order for the user to
benefit from the fluent logging API. However, existing frameworks
*must* migrate to the ServiceLoader mechanism. The resulting
internal changes are detailed in the FAQ page.
http://www.slf4j.org/faq.html#changesInVersion200
The 2.0.x series builds upon the the 1.8.x series which was
modularized per Java Platform Module System (JPMS/Jigsaw).
The 2.0.x series requires Java 8.
Please refer to the the news page for more details on this
release:
http://www.slf4j.org/news.html
Binary compatibility:
Mixing mixing different versions of slf4j-api.jar and SLF4J
provider can cause problems. For example, if you are using
slf4j-api-2.0.0.jar, then you should also use
slf4j-simple-2.0.0.jar, using slf4j-simple-1.5.5.jar will not
work.
With the exception of the fluent API (new in SLF4J 2.0.x), 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 provider 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 provider 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ü
Hello all,
I am happy to announce the release of logback version 1.3.0-alpha10,
the best performing logback yet. It requires slf4j-api version
2.0.0-alpha4 or later.
For benchmarking figures please see:
http://logback.qos.ch/performance.html
This version supports the fluent-API introduced in SLF4J
2.0.x. It also supports Jigsaw/Java9 modularization.
Joran, logback's configuration system, has been rewritten to use
an internal representation model which can be processed
separately. Given the breadth of the changes, support for
SiftingAppender and Groovy configuration have been dropped
temporarily.
No new features are available in this version. Future releases
will gradually introduce new features made possible by Joran
representation model.
The 1.3.x series requires Java 8 at runtime. If you wish to build
logback from source, you will need Java 9.
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 Gülcü
Hello all,
I am happy to announce the release of logback version
1.3.0-alpha8. It requires slf4j-api version 2.0.0-alpha4 or
later.
This version supports the fluent-API introduced in SLF4J
2.0.x. It also supports Jigsaw/Java9 modularization.
Joran, logback's configuration system, has been rewritten to use
an internal representation model which can be processed
separately. Given the breadth of the changes, support for
SiftingAppender and Groovy configuration have been dropped
temporarily.
No new features are available in this version. Future releases
will gradually introduce new features made possible by Joran
representation model.
The 1.3.x series requires Java 8 at runtime.
If you wish to build logback from source, you will need Java 9.
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 Gülcü
Hello all,
I am pleased to announce SLF4J 2.0.0-alpha4. This release
contains the slf4j-jdk-platform module which adds support for the
Java Platform Logging API (JEP 264).
The 2.0.x series introduces a backward-compatible fluent logging
API. By backward-compatible, we mean that existing logging
frameworks do not have to be changed in order for the user to
benefit from the fluent logging API. However, existing frameworks
*must* migrate to the ServiceLoader mechanism. The resulting
internal changes are detailed in the FAQ page.
http://www.slf4j.org/faq.html#changesInVersion200
The 2.0.x series builds upon the the 1.8.x series which was
modularized per Java Platform Module System (JSR 376).
The 2.0.x series requires Java 8.
Please refer to the the news page for more details on this release:
http://www.slf4j.org/news.html
Binary compatibility:
Mixing mixing different versions of slf4j-api.jar and SLF4J provider
can cause problems. For example, if you are using slf4j-api-2.0.0.jar,
then you should also use slf4j-simple-2.0.0.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 provider 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 provider 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ü
Hello all,
I am happy to announce the release of logback version 1.3.0-alpha7. It
reuires slf4j-api version 2.0.0-alpha3 or later.
This version supports the fluent-API introduced in SLF4J
2.0.x. It also supports Jigsaw/Java9 modularization.
Joran, logback's configuration system, has been rewritten to use
an internal representation model which can be processed
separately. Given the breadth of the changes, support for
SiftingAppender and Groovy configuration have been dropped
temporarily.
No new features are available in this version. Future releases
will gradually introduce new features made possible by Joran
representation model.
The 1.3.x series requires Java 8 at runtime.
If you wish to build logback from source, you will need Java 9.
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 Gülcü
_________________
Hello all,
I am pleased to announce SLF4J 2.0.0-alpha3. The 2.0.x series
introduces a backward-compatible fluent logging API. By
backward-compatible, we mean that existing logging frameworks do not
have to be changed in order for the user to benefit from the fluent
logging API. However, existing frameworks *must* migrate to the
ServiceLoader mechanism. The resulting internal changes are detailed in
the FAQ page.
http://www.slf4j.org/faq.html#changesInVersion200
The 2.0.x series builds upon the the 1.8.x series which was modularized
per Java Platform Module System (JSR 376).
The 2.0.x series requires Java 8.
Please refer to the the news page for more details on this release:
http://www.slf4j.org/news.html
Binary compatibility:
Mixing mixing different versions of slf4j-api.jar and SLF4J provider
can cause problems. For example, if you are using slf4j-api-2.0.0.jar,
then you should also use slf4j-simple-2.0.0.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 provider 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 provider 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ü
___________________
