You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a lot of places where exceptions are caught and logged using printStackTrace or System.err.println. It's not ideal for production systems where errors are generally written to log files instead of stderr.
Would be great if they can be replaced with an actual logger like slf4j, or maybe it should always bubble up exceptions to the caller and leave it to them to decide how exceptions should be handled.
If you think it's a good idea, we have a patch which replaces printStackTrace and System.err.println with slf4j Logger.error.
The text was updated successfully, but these errors were encountered:
There are a lot of places where exceptions are caught and logged using
printStackTrace
orSystem.err.println
. It's not ideal for production systems where errors are generally written to log files instead of stderr.Would be great if they can be replaced with an actual logger like
slf4j
, or maybe it should always bubble up exceptions to the caller and leave it to them to decide how exceptions should be handled.If you think it's a good idea, we have a patch which replaces
printStackTrace
andSystem.err.println
with slf4jLogger.error
.The text was updated successfully, but these errors were encountered: