vy commented on issue #3904: URL: https://github.com/apache/logging-log4j2/issues/3904#issuecomment-3242633150
@jakub-id, starting with version `2.24.0`, Log4j API is embraced as the target logging API for both Log4j 2 and Log4j 3. Hence, Log4j 3 does not contain a Log4j API module, but instead implements "the" Log4j API developed in Log4j 2 branch. This ensures Log4j 2 users can safely migrate to Log4j 3 without any Log4j API compatibility concerns. (See [Log4j 3 API docs](https://logging.apache.org/log4j/3.x/manual/api.html).) As a result, Log4j 3 does not ship a separate `log4j-slf4j-impl`, which bridges SLF4J calls to Log4j API, and you can safely use `log4j-slf4j-impl-2.x` in Log4j 3. But we strongly recommend our users to, instead of explicitly providing each artifact version, **use `log4j-bom`** (see [Log4j 3 BOM docs](https://logging.apache.org/log4j/3.x/manual/installation.html#bom)) and leverage the dependencies managed by it. @jakub-id, would you mind retrying your experiment after importing `log4j-bom` and removing explicit version numbers, please? -- 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
