Am 12.07.2022 um 17:31 schrieb Joakim Erdfelt:
Eclipse Jetty dev here.
We've been using slf4j 2.0.x for production servers since Dec 2020
without issue.
It's been highly reliable for the millions of servers that use Eclipse
Jetty 10+.
We chose slf4j 2.0.x as it properly supported JPMS, which is an
optional execution mode for our server that many folks use.
- Joakim
That really makes me wonder why slf4j 2.0 has never been released as
stable version? The current non-stable situation is a show-stopper for
us, we are not allowed to use it in productive code.
Thanks,
- Daniel
On Tue, Jul 12, 2022 at 9:28 AM Christoph Briem
<christoph.br...@gmail.com> wrote:
Hi all,
sorry if this has been answered already anywhere else. But I
couldn't find an answer so far.
We're currently evaluating moving further from Java 11 to Java 17.
We've realized that we also have to update slf4j, to either 1.8.x
or 2.0.x.
Right now, both minor versions are not marked as stable, and we're
somehow reluctant using an alpha or beta version.
My question is: What is your recommendation for people moving on
to Java 17? Use 1.8.x or 2.0.0.x? Or wait until a stable release
is out? Or is there a way to get 1.7.x running on Java 17?
Thanks for your help,
Chris
_______________________________________________
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
_______________________________________________
slf4j-user mailing list
slf4j-user@qos.ch
http://mailman.qos.ch/mailman/listinfo/slf4j-user
