[
https://issues.apache.org/jira/browse/LOG4J2-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379113#comment-16379113
]
Matt Sicker commented on LOG4J2-1705:
-------------------------------------
A new issue would be great. Make sure to mention this issue there.
As for a more thorough code review, I have time this week here and there to go
through it in more detail. In the meantime, the only thing I can suggest is
perhaps experimenting with a stand alone Logger class specific to Kotlin. See
for example the Logger class in log4j-api-scala which doesn't include the
parameterized logging parameters for example because Scala supports template
strings (similar to Kotlin).
As it is now, a Kotlin user can just create a Logger with the Java API along
with some annoyances that you seem to have covered in the Kotlin extension.
> Kotlin wrapper for Log4j 2 API
> ------------------------------
>
> Key: LOG4J2-1705
> URL: https://issues.apache.org/jira/browse/LOG4J2-1705
> Project: Log4j 2
> Issue Type: New Feature
> Components: API
> Reporter: Raman Gupta
> Priority: Major
>
> Similar to LOG4J2-1181 for Scala, provide a Kotlin wrapper for the Log4j 2
> API that makes use of Kotlin features like delegates and string interpolation.
> If there is interest in this, I'd like to contribute a patch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
