vy commented on issue #3904: URL: https://github.com/apache/logging-log4j2/issues/3904#issuecomment-3244123795
> I'm still curious: why are there no `3.0.0-beta3` artifacts for log4j-slf4j and the BOM points back to `2.24.1`? `<ai-assistance>` Why does Log4j 3 target the old Log4j 2 API? - **Drop-in replacement** – No code changes, just swap the Log4j Core dependency. - **Smooth migration** – Avoids the pain of introducing a new API. - **Ecosystem stability** – Prevents breaking frameworks and libraries. - **Backend focus** – Log4j 3 improves internals while keeping the API. **In short:** Log4j 3 = new core, same API — upgrades without disruption. `</ai-assistance>` Let me know if this does not answer your question. @jakub-id, I think, I've made some progress. Would you mind implementing the following changes and reporting back the result, please? 1. In `/pom.xml`, set the `log4j2.version` to `3.0.0-beta3` 2. In `/util/pom.xml`, replace `log4j-slf4j-impl` dependency with `log4j-slf4j2-impl` (Because you're using SLF4J 2) 3. In `/server/pom.xml`, exclude `org.slf4j:jcl-over-slf4j` from `org.apache.solr:solr-solrj`, and add `commons-logging:commons-logging:1.3.5:test` dependency instead (See [Installing JCL-to-Log4j Bridge](https://logging.apache.org/log4j/3.x/manual/installation.html#impl-core-bridge-jcl)) 4. In `/server/pom.xml`, replace `log4j-slf4j-impl` dependency with `log4j-slf4j2-impl` 5. In `/server/pom.xml`, exclude `org.apache.logging.log4j:log4j-1.2-api` from `org.folio.okapi:okapi-core` (I suspect a bug in `log4j-1.2-api` here, I will check it later.) 6. In `/client/pom.xml`, replace `log4j-slf4j-impl` dependency with `log4j-slf4j2-impl` -- 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: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
