-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move from SLF4j to Java 9+ System.Logger and provide binding for logback out of the box #7043
Comments
I don't think this is a good idea. The
Also, since |
Yeah it is just here for consideration, it is pretty obvious at runtime slf4j and logback would still be needed, but if that could be made an optional dependency it means less is needed. The question is do we need any of the features of these libraries in Micronaut Core. It is clear that certain features (MDC comes to mind) are required for production level applications |
We could also make our own logging adapter at that point |
FYI: Some comments about
|
Just for reference, that's not quite correct. |
I wonder which are such cool features in other logging frameworks not available in JUL and used in micronaut... Log4J vulnerability CVE-2021-45046 teaches to keep logging simple |
@stefanofornari slf4j is a facade that allows users to pick their own logging framework. This is much more difficult with JUL. We do not want to force people to use JUL over other, more capable frameworks like logback. |
The real question is what are the logging facade features that Micronaut needs that are not available in |
Feature description
Since Java 9 SLF4J is no longer necessary and we should move logging to System.Logger
Ref https://www.baeldung.com/java-9-logging-api
This eliminates the need for an additional dependency
The text was updated successfully, but these errors were encountered: