Re: [jetty-users] Use of experimental slf4j/logback in Jetty 10?

[Joakim Erdfelt <joakim@xxxxxxxxxxx>]

We have reports from many websites running on Jetty slf4j-api 2.0 and logback 1.3 in production today without issue.

That being said, we chose slf4j-api 2.0 as it properly supports JPMS, one of the highlight features of Jetty 10+.

Logback 1.3 also supports JPMS properly.

Our usage is slf4j-api, but we internally don't use the slf4j-api 2.0 specific API features.

That means you can manually downgrade to slf4j-api 1.x if you so desire, and use that old implementation, across the board.

Note that slf4j-api 1.x does NOT support JPMS, so if you are running that way, you'll need to stick with slf4j-api 2.0.

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Wed, Dec 22, 2021 at 12:57 PM Cantor, Scott <cantor.2@xxxxxxx> wrote:

Is there a particular reason why Jetty 10 is including non-production versions of logging libraries? Needless to say, that's a bit offputting in light of recent events.

I realize it doesn't preclude applications using the stable versions, but I imagine the actual Jetty support for slf4j is limited to the non-production API version?

-- Scott



_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users