-
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
Use SLF4J instead of java.util.logging #113
Labels
Milestone
Comments
Merged
Hi, As I said here, I don't exclude replacing JUL with SL4J. Thank you for the PR! I added a couple of notes there. Kr |
Hi, I've merged your PR, thank you! Hence, I'm closing this issue. Kr |
Thank you :) |
Hi, fact.getValue() == null ? "null" : fact.getValue().toString() I think |
@wg1j good point! |
@wg1j done here: 4b7ed47 |
This was referenced Mar 21, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using java.util.logging for logging has a lot of side effect. See this
http://glauche.de/2009/09/09/java-util-logging-vs-slf4j/
For example, we are using this lib into a Grails 2 application. But it doesn't use our logging config. We need to replicate logs formats, because we are using Kibana and we need a predefined format.
I think it could be great using slf4j instead of java.util.logging. This resolves our problem and the performance should be better.
The text was updated successfully, but these errors were encountered: