Hi Piotr,
Thank you very much for your help. I've understood how it works. I just wonder
did you decide to go this way because
you plan to continue version 2?
Best regards, Pavel
On 11/28/24 13:40, Piotr P. Karwasz wrote:
Hi Pavel,
On 28.11.2024 11:36, PavelTurk wrote:
I work only with JPMS and decided to test log4j 3. As I understand the last
version is 3.0.0-beta3
but there is no log4j-slf4j2-impl for this version:
https://mvnrepository.com/artifact/org.apache.logging.log4j/log4j-slf4j2-impl
Could anyone say how to route slf4j2 messages to log4j in 3.0.0-beta3?
All the API-to-API bridges are still available, they are just not published
together with Log4j Core 3, since they don't depend on Log4j Core (see release
notes[1]).
Since both Log4j Core 2.24.2 and Log4j Core 3.0.0-beta3 implement Log4j API
2.24, the right version of `log4j-slf4j2-impl` to use is `2.24.2`.
I understand that the fact Log4j Core 3 implements Log4j API 2 might be
confusing, therefore we recommend all users to use `log4j-bom` to manage the
version of Log4j Core. The usage of the BOM will guarantee you that the right
version of Log4j API and the logging bridges will be used, even if other
libraries in your dependency stack specify a different version of Log4j API.
Piotr
[1]
https://logging.apache.org/log4j/3.x/release-notes.html#release-notes-3-0-0-beta3
[2] https://logging.apache.org/log4j/3.x/components.html#log4j-bom
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
