[
https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350664#comment-15350664
]
Mikael Ståldal commented on LOG4J2-1181:
----------------------------------------
Implementing flow tracing properly is a bit tricky since a lot of the logic is
in {{AbstractLogger}} which I have no access to. Currently I just call through
to the methods in the wrapped {{Logger}}, but then the location info will be
wrong, and I cannot make macros without having double {{isEnabled}} check.
It would be nice if we could expose the flow tracing in {{AbstractLogger}}, or
maybe break it out from there and put it in a new class.
> Scala wrapper for Log4j 2 API
> -----------------------------
>
> Key: LOG4J2-1181
> URL: https://issues.apache.org/jira/browse/LOG4J2-1181
> Project: Log4j 2
> Issue Type: New Feature
> Components: API
> Affects Versions: 2.4.1, 2.5, 2.6, 2.6.1
> Reporter: Mikael Ståldal
>
> Scala wrapper for Log4j 2 API which makes use of Scala features like macros
> and string interpolation.
> Inspired from [Typesafe's Scala
> Logging|https://github.com/typesafehub/scala-logging] but should use Log4j 2
> directly and expose its features.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
