ppkarwasz commented on issue #4045: URL: https://github.com/apache/logging-log4j2/issues/4045#issuecomment-3959109041
Hi @z0mb1ek, Unfortunately, AI-generated noise is currently consuming a large portion of our bandwidth (see #4052), but advancing **Log4j 3** remains my top priority. Personally, I would prefer to see `3.0.0` released **before** `2.26.0`, though each maintainer is free to focus on what they consider most impactful. @garydgregory, There is no API leakage from Jackson in Log4j Core. However: * Jackson 3 has a **Java 17 baseline**, which means it cannot be directly used by Log4j Core 2. * Migrating to Jackson 3 would be a **breaking change**: the Jackson dependency is currently `optional`, and users would need to explicitly update their own dependency sets. If you would like to reopen this issue and support Jackson 3 via reflection, I would not oppose it. That said, I believe our limited time is better spent pushing Log4j Core 3 forward. -- 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]
