[
https://issues.apache.org/jira/browse/LOG4J2-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602094#comment-17602094
]
ASF subversion and git services commented on LOG4J2-3589:
---------------------------------------------------------
Commit 70de14fcc1dfb74173846bf93e8c90a0bb275fc7 in logging-log4j2's branch
refs/heads/master from Piotr P. Karwasz
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=70de14fcc1 ]
LOG4J2-3589 - Avoid storing strong references to the LoggerContext
> 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
> Fix For: 2.19.0
>
>
> 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)
