[
https://issues.apache.org/jira/browse/LOG4J2-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16148963#comment-16148963
]
Jason Tedor commented on LOG4J2-2023:
-------------------------------------
Would you please link to the relevant mailing list discussion? I have looked on
the [user list](http://mail-archives.apache.org/mod_mbox/logging-log4j-user/)
and the [dev list](http://mail-archives.apache.org/mod_mbox/logging-log4j-dev/)
(which for some reason is only archived through April) and have not
successfully found it. I also looked at the commit log. I would like to
understand the reasoning behind this breaking change. In particular, was the
impact this would have on local and anonymous classes considered?
I think the entire community would benefit from more verbose descriptions of
reasoning on issues and in commit messages.
> Use a class' canonical name instead of name to create its logger name
> ---------------------------------------------------------------------
>
> Key: LOG4J2-2023
> URL: https://issues.apache.org/jira/browse/LOG4J2-2023
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
> Reporter: Gary Gregory
> Assignee: Gary Gregory
> Fix For: 2.9
>
>
> Use a class' canonical name instead of name to create its logger name
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
