[jira] [Comment Edited] (LOG4J2-3147) Kuberenetes Lookup referring to wrong Spring classname

["Matthew McMahon (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404393#comment-17404393 ] 

Matthew McMahon edited comment on LOG4J2-3147 at 8/25/21, 12:29 PM:
--------------------------------------------------------------------

As requested, merge request is checking for both the old and new class


was (Author: maccamlc):
The issue seems to be that the rename of the package already occured, so if you try and use 1.14.0 or 1.14.1 like I did, then it is not working. This is technically a bug fix in my mind.

> 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)