Hello all,
I am thrilled to announce the simultaneous release of logback versions
1.3.0 and 1.4.0. Both versions require slf4j-api version 2.0.0 or
later.
Given that downstream users are likely to depend on either Java EE (in
the javax namespace) or on Jakarta EE (in the jakarta namespace) in
their projects, it was deemed important for logback to support both EE
alternatives.
As such, logback 1.3.x supports Java EE whereas logback 1.4.x supports
Jakarta EE, otherwise the two versions are feature identical.
Both 1.3.x and 1.4.x series require the fluent-API introduced in SLF4J
2.0.x.
The 1.3.x series requires Java 8 at runtime. If you wish to build
logback from source, you will need Java 9. Reproducible builds require
Java 18.
The 1.4.x series requires Java 11 at build time and at runtime.
------------------
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 was dropped
temporarily and reintroduced in logback version 1.3.0-alpha16. Support
for Groovy configuration was dropped for security reasons but was
recovered by Tucker Pelletier (virtualdogbert). See:
https://github.com/virtualdogbert/logback-groovy-config
For benchmarking figures please see:
http://logback.qos.ch/performance.html
Recent logback releases are reproducible. This means that anyone
checking out the code corresponding to the release version from github
and building that local copy, will get obtain an identical binary to
the binary found on Maven central. Note that due to issue MJAR-275
with the module-info.java produced in earlier java versions,
reproducible builds require Java 18.
Donations and sponsorship
You can also support SLF4J/logback/reload4j projects via donations and
sponsorship. We thank our current supporters and sponsors for their
continued contributions.
Sponsorship link: https://github.com/sponsors/qos-ch
Announcement mailing list:
You can receive SLF4J/logback/reload4j related announcements by
subscribing QOS.ch announce list, please visit the following URL.
http://www.qos.ch/mailman/listinfo/announce
Enjoy,
--
Ceki Gülcü
Hello all,
After a long estation period, I am very pleased to announce SLF4J
version 2.0.0.
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.
Donations and sponsorship
You can also support SLF4J/logback/reload4j projects via donations and
sponsorship. We thank our current supporters and sponsors for their
continued contributions.
Sponsorship link: https://github.com/sponsors/qos-ch
Announcement mailing list:
You can receive SLF4J/logback/reload4j related announcements by
subscribing QOS.ch announce list, please visit the following URL.
http://www.qos.ch/mailman/listinfo/announce
Enjoy,
-- Ceki Gülcü
Hello all,
I am happy to announce the release of logback version 1.3.0-beta0. It
requires slf4j-api version 2.0.0-beta1 or later.
Although marked as beta, it should be considered a stable version.
Logback 1.3.0-GA should be released later this month.
The 1.3.x series 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 was dropped
temporarily and reintroduced in logback version 1.3.0-alpha16. Support
for Groovy configuration was dropped for security reasons but was
recovered by Tucker Pelletier (virtualdogbert). See:
https://github.com/virtualdogbert/logback-groovy-config
Note that new features were introduced this version. Future releases
will gradually introduce new features made possible by Joran
representation model.
For benchmarking figures please see:
http://logback.qos.ch/performance.html
The 1.3.x series requires Java 8 at runtime. If you wish to build
logback from source, you will need Java 9. Reproducible builds require
Java 18.
Recent logback releases are reproducible. This means that anyone
checking out the code corresponding to the release version from github
and building that local copy, will get obtain an identical binary to the
binary found on Maven central. Note that due to issue MJAR-275 with the
module-info.java produced in earlier java versions, reproducible builds
require Java 18.
Donations and sponsorship
You can also support SLF4J/logback/reload4j projects via donations and
sponsorship. We thank our current supporters and sponsors for their
continued contributions.
Sponsorship link: https://github.com/sponsors/qos-ch?o=esb
Announcement mailing list:
You can receive SLF4J/logback/reload4j related announcements by
subscribing QOS.ch announce list, please visit the following URL.
http://www.qos.ch/mailman/listinfo/announce
Enjoy,
--
Ceki Gülcü
Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch
Hello all,
I am pleased to announce SLF4J 2.0.0-beta0. After a long debate, this
release adds the methods setMessage(String),
setMessage(Supplier<String>) and log() methods to the
LoggingEventBuilder interface.
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.
Donations and sponsorship
You can also support SLF4J/logback/reload4j projects via donations and
sponsorship. We thank our current supporters and sponsors for their
continued contributions.
Sponsorship link: https://github.com/sponsors/qos-ch
Announcement mailing list:
You can receive SLF4J/logback/reload4j related announcements by
subscribing QOS.ch announce list, please visit the following URL.
http://www.qos.ch/mailman/listinfo/announce
Enjoy,
--
Ceki Gülcü
