[
https://issues.apache.org/jira/browse/LOG4J2-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17332806#comment-17332806
]
Ralph Goers commented on LOG4J2-3083:
-------------------------------------
I have no idea, but Log4j doesn't control what configuration files you can
access via Spring profiles. Looking at the SLF4J code I see no difference in
what the two methods you are referencing actually do. LoggerFactory.getLogger()
call getILoggerFactory() under the covers and then calls getLogger().
Closing as none of this has anything to do with Log4j.
> Why the logger get by Slf4j LoggerFactory.getILoggerFactory() can only use
> current LoggerContext
> ------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-3083
> URL: https://issues.apache.org/jira/browse/LOG4J2-3083
> Project: Log4j 2
> Issue Type: Question
> Affects Versions: 2.13.3
> Environment: Spring Boot 2.4.5
> Slf4j
> Reporter: wanghao
> Priority: Major
> Labels: newbie
>
> In SpringBoot project with +test+ profile,
> org.slf4j.LoggerFactory.getLogger("xxx") can get test profile LoggerContext
> and read configuration from log4j2-test.xml.
> But
> org.slf4j.LoggerFactory.getILoggerFactory().getLogger("xxx") can only get
> current LoggerContext and read configuration from log4j2.xml.
>
> Is it designed like this? Why?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
