Thanka Joakim. Good to know.

I am curious, were you using Java Platform Logging API (JEP 264) at all?

Cheers,

--
Ceki

On 30/08/2021 20:35, Joakim Erdfelt wrote:
Thank you for the release.

Eclipse Jetty has been at 2.0.0-alpha4 since it was released.
We've been using it successfully on classpath and module-path.

Started the upgrade to 2.0.0-alpha5 now - https://github.com/eclipse/jetty.project/pull/6684 <https://github.com/eclipse/jetty.project/pull/6684>

- Joakim

On Mon, Aug 30, 2021 at 11:35 AM Ceki Gülcü <c...@qos.ch <mailto:c...@qos.ch>> wrote:

    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
    <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 <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 <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
    <http://www.qos.ch/mailman/listinfo/announce>

    You may also receive announcements via twitter:

    https://twitter.com/qos_ch <https://twitter.com/qos_ch>

    Enjoy,

-- Ceki Gülcü
    _______________________________________________
    slf4j-user mailing list
    slf4j-user@qos.ch <mailto:slf4j-user@qos.ch>
    http://mailman.qos.ch/mailman/listinfo/slf4j-user
    <http://mailman.qos.ch/mailman/listinfo/slf4j-user>


_______________________________________________
slf4j-user mailing list
slf4j-user@qos.ch
http://mailman.qos.ch/mailman/listinfo/slf4j-user

_______________________________________________
slf4j-user mailing list
slf4j-user@qos.ch
http://mailman.qos.ch/mailman/listinfo/slf4j-user

Reply via email to