[
https://issues.apache.org/jira/browse/LOG4J2-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-3589:
--------------------------------
Description:
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.
was: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.
> 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)
