12.0.x Remove usage of Slf4j fluent api by olamy · Pull Request #14642 · jetty/jetty.project (original) (raw)
that may beclosed by this pull request
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is also an occurrence of atInfo() that needs to be fixed.
sbordet previously approved these changes Mar 10, 2026
@olamy Thanks for this patch! Out of curiosity, is this just a temporary workaround, or is Jetty permanently moving away from the SLF4J fluent APIs? Since Kafka can't adopt SLF4J 2 until Kafka 5.0, we were planning to use shadowing to tackle the compatibility issue. If the Jetty community decides to drop the fluent APIs entirely, we could upgrade Jetty much more easily and avoid the shadowing hack altogether
This is a temporary workaround for Jetty 12.0.x.
Jetty 12.1.x is already using the fluent API much more extensively and there is no plan to go back.
On a similar note, Jetty 13.0.x, in the working for this year, will likely require Java 25.
Signed-off-by: Olivier Lamy olamy@apache.org
Signed-off-by: Olivier Lamy olamy@apache.org
Signed-off-by: Olivier Lamy olamy@apache.org
Is there an ETA for the next 12.0.x release? I’m hoping to see if this patch can be included.
@sbordet Thanks for sharing, this is helpful. Noted!
@sbordet I can't see any information about the next 12.0.X release, I checked the dev and users lists, github issues/prs/tags. Is there a way for users to follow the project's plans and progress?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})