You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/09/06 19:31:00 UTC

[jira] [Commented] (LOG4J2-3589) Allow plugins to be injected with the LoggerContext

    [ https://issues.apache.org/jira/browse/LOG4J2-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600956#comment-17600956 ] 

ASF subversion and git services commented on LOG4J2-3589:
---------------------------------------------------------

Commit bb0c70ec1afe867a52efee873fabb3197dabeae8 in logging-log4j2's branch refs/heads/master from Ralph Goers
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=bb0c70ec1a ]

LOG4J2-3589 - Allow Plugins to be injected with the LoggerContext reference


> Allow plugins to be injected with the LoggerContext
> ---------------------------------------------------
>
>                 Key: LOG4J2-3589
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3589
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Configuration
>    Affects Versions: 2.18.0
>            Reporter: Ralph Goers
>            Priority: Major
>
> Log4j-Spring-Boot needs access to the LoggerContext. The way it is getting it now is pretty kludgy. It would be better if the LoggerContext was injected into the plugins.
> Note: This should apply to only release-2.x as it is expected that the DI system in 3.0 should handle this already.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)