Details
-
Bug
-
Resolution: Fixed
-
Major
-
1.7.25
-
Slf4j-jdk14 binding
Description
When using SubstituteLogger with JDK14LoggerAdapter (obtained regularly via LoggerFactory) the output always gives SubstituteLogger as the caller. A programmer would be interested in the class/method of his code.
The issue is that JDK14LoggerAdapter.fillCallerData() does not take into account that SubstituteLogger can be the direct caller, and it is needed to go one level deeper.
This issue is similar to one reported to LogBack.
Attachments
Issue Links
- relates to (in)
-
LOGBACK-1100 Skip SubstituteLogger from caller data
- Open