<div dir="ltr">Thank you for the release.<div><br></div><div>Eclipse Jetty has been at 2.0.0-alpha4 since it was released.</div><div>We've been using it successfully on classpath and module-path.</div><div><br></div><div>Started the upgrade to 2.0.0-alpha5 now - <a href="https://github.com/eclipse/jetty.project/pull/6684">https://github.com/eclipse/jetty.project/pull/6684</a></div><div><br></div><div>- Joakim</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 30, 2021 at 11:35 AM Ceki Gülcü <<a href="mailto:ceki@qos.ch">ceki@qos.ch</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello all,<br>
<br>
I am pleased to announce SLF4J 2.0.0-alpha5. This release fixes<br>
an issue with Java Platform Logging API (JEP 264) support when<br>
running under the class-path (but not the module-path). JEP 264<br>
support is new in SLF4J 2.0.0-alpha4.<br>
<br>
The 2.0.x series introduces a backward-compatible fluent logging<br>
API. By backward-compatible, we mean that existing logging<br>
frameworks do not have to be changed in order for the user to<br>
benefit from the fluent logging API. However, existing frameworks<br>
*must* migrate to the ServiceLoader mechanism. The resulting<br>
internal changes are detailed in the FAQ page.<br>
<br>
<a href="http://www.slf4j.org/faq.html#changesInVersion200" rel="noreferrer" target="_blank">http://www.slf4j.org/faq.html#changesInVersion200</a><br>
<br>
The 2.0.x series builds upon the the 1.8.x series which was<br>
modularized per Java Platform Module System (JPMS/Jigsaw).<br>
<br>
The 2.0.x series requires Java 8.<br>
<br>
Please refer to the the news page for more details on this<br>
release:<br>
<br>
<a href="http://www.slf4j.org/news.html" rel="noreferrer" target="_blank">http://www.slf4j.org/news.html</a><br>
<br>
Binary compatibility:<br>
<br>
Mixing mixing different versions of slf4j-api.jar and SLF4J<br>
provider can cause problems. For example, if you are using<br>
slf4j-api-2.0.0.jar, then you should also use<br>
slf4j-simple-2.0.0.jar, using slf4j-simple-1.5.5.jar will not<br>
work.<br>
<br>
With the exception of the fluent API (new in SLF4J 2.0.x), from<br>
the client's perspective all versions of slf4j-api are<br>
compatible. Client code compiled with slf4j-api-N.jar will run<br>
perfectly fine with slf4j-api-M.jar for any N and M. You only<br>
need to ensure that the version of your provider matches that of<br>
the slf4j-api.jar. You do not have to worry about the version of<br>
slf4j-api.jar used to compile a given dependency in your<br>
project. You can always use *any* version of slf4j-api.jar, and<br>
as long as the version of slf4j-api.jar and its provider match,<br>
you should be fine.<br>
<br>
Downloading SLF4J:<br>
<br>
You can download SLF4J, including full source code, class files<br>
and documentation on our download page:<br>
<br>
<a href="http://www.slf4j.org/download.html" rel="noreferrer" target="_blank">http://www.slf4j.org/download.html</a><br>
<br>
Announcement mailing list:<br>
<br>
You can receive SLF4J related announcements by subscribing to the<br>
SLF4J announce mailing list. To subscribe to QOS.ch announce<br>
list, please visit the following URL.<br>
<br>
<a href="http://www.qos.ch/mailman/listinfo/announce" rel="noreferrer" target="_blank">http://www.qos.ch/mailman/listinfo/announce</a><br>
<br>
You may also receive announcements via twitter:<br>
<br>
<a href="https://twitter.com/qos_ch" rel="noreferrer" target="_blank">https://twitter.com/qos_ch</a><br>
<br>
Enjoy,<br>
<br>
-- <br>
Ceki Gülcü<br>
_______________________________________________<br>
slf4j-user mailing list<br>
<a href="mailto:slf4j-user@qos.ch" target="_blank">slf4j-user@qos.ch</a><br>
<a href="http://mailman.qos.ch/mailman/listinfo/slf4j-user" rel="noreferrer" target="_blank">http://mailman.qos.ch/mailman/listinfo/slf4j-user</a></blockquote></div>