ppkarwasz commented on issue #3969: URL: https://github.com/apache/logging-log4j2/issues/3969#issuecomment-3456568762
Hi @seregamorph, > We expect to resolve the mismatch in the upcoming `2.26.0` release. @vy’s statement refers to work planned for Log4j `2.26.0`, that will affect integration with Spring Boot `4.1.x` and beyond. It doesn’t apply to the issue you’re encountering here. In your case, the root cause is different. The `log4j-spring-boot` module, which contains the `Log4j2SpringBootLoggingSystem` class, was designed specifically for **Spring Boot 2.x** to address some shortcomings of Spring Boot's built-in `Log4J2LoggingSystem`. Starting with **Spring Boot 3.x**, this module became unnecessary because its functionality was merged into Spring Boot. As a result: * `log4j-spring-boot` is **not binary compatible** with Spring Boot 4.x * It has effectively been **deprecated** since Spring Boot 3.x * We currently **do not plan to release** a `log4j-spring-boot4` module If your project targets Spring Boot **3.x or 4.x**, the recommended solution is simply to **remove** the `log4j-spring-boot` dependency and rely on the native Spring Boot Log4j2 integration, which already provides equivalent functionality. Could you share why your project still depends on `log4j-spring-boot`? Are there specific features or configuration options from that module that you feel are missing in the Spring Boot Log4j2 integration? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
