[
https://issues.apache.org/jira/browse/LOG4J2-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404269#comment-17404269
]
Volkan Yazici commented on LOG4J2-3147:
---------------------------------------
Plainly renaming this package literal will create a backward compatibility
problem for those who are running the updated version of Log4j in combination
with an old Spring dependency, AFAIC. We need to check for both the old and the
new package. [~maccamlc], mind submitting a GitHub PR for this?
> 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)
