[
https://issues.apache.org/jira/browse/LOG4J2-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405018#comment-17405018
]
ASF subversion and git services commented on LOG4J2-3147:
---------------------------------------------------------
Commit 1a24f7a89452042d997489d71ea5b37398ef1a2d in logging-log4j2's branch
refs/heads/master from Matthew McMahon
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=1a24f7a ]
LOG4J2-3147 Fix Spring package check in KubernetesLookup. (#569)
Co-authored-by: Matthew McMahon <matthew.mcma...@thetradedesk.com>
> Kuberenetes Lookup referring to wrong Spring classname
> ------------------------------------------------------
>
> Key: LOG4J2-3147
> URL: https://issues.apache.org/jira/browse/LOG4J2-3147
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.14.0
> Reporter: Matthew McMahon
> Priority: Major
>
> I am having trouble getting the Kubernetes Lookup to work in my Spring Boot
> app.
> I've noticed that isSpringIncluded is getting set to false, as the class in
> question has changed it's package name, and lives in log4j-spring-boot.
> {code}
> private static final boolean isSpringIncluded =
> LoaderUtil.isClassAvailable("org.apache.logging.log4j.spring.cloud.config.client.SpringEnvironmentHolder");
> {code}
> This probably needs to be updated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
