[ https://jira.qos.ch/browse/SLF4J-445?page=com.atlassian.jira.plugin.system.i... ] Ceki Gülcü resolved SLF4J-445. ------------------------------ Resolution: Fixed Fixed in [commit 9928d|https://github.com/qos-ch/slf4j/commit/9928d80daf022e]

Skip SubstituteLogger from caller data (slf4j-jdk14) ----------------------------------------------------

Key: SLF4J-445 URL: https://jira.qos.ch/browse/SLF4J-445 Project: SLF4J Issue Type: Bug Components: Implementations Affects Versions: 1.7.25 Environment: Slf4j-jdk14 binding Reporter: Alexander Yevsyukov Assignee: Ceki Gülcü Labels: consoleoutput, substitution Fix For: 1.8.0-beta5

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|https://jira.qos.ch/browse/LOGBACK-1100].

-- This message was sent by Atlassian JIRA (v7.3.1#73012)