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
I noticed that when printing System.out or System.err the line numbers are incorrect in the final log message. The incorrect line numbers comes from LogLevel class where the message is given to logger.
In SLF4JPrintStreamDelegate ClassOrigin.getCallOrigin could also easily resolve the correct line number. SLF4J logger cannot take in line number, but we could put it in front of message for example. It could be customizable feature how to add line number to message or format message. This requires new interface to sysout-over-slf4j which user could implement.
Even some indication in the log message about the wrong line number would help.
The text was updated successfully, but these errors were encountered:
I noticed that when printing System.out or System.err the line numbers are incorrect in the final log message. The incorrect line numbers comes from LogLevel class where the message is given to logger.
In SLF4JPrintStreamDelegate ClassOrigin.getCallOrigin could also easily resolve the correct line number. SLF4J logger cannot take in line number, but we could put it in front of message for example. It could be customizable feature how to add line number to message or format message. This requires new interface to sysout-over-slf4j which user could implement.
Even some indication in the log message about the wrong line number would help.
The text was updated successfully, but these errors were encountered: