You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by PavelTurk <pa...@gmail.com> on 2024/11/28 10:36:18 UTC
There is no log4j-slf4j2-impl in 3.0.0-beta3
Hello everyone.
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?
Best regards, Pavel
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: There is no log4j-slf4j2-impl in 3.0.0-beta3
Posted by Matt Sicker <ma...@musigma.org>.
Perfect.
> On Dec 2, 2024, at 12:31, Piotr P. Karwasz <pi...@mailing.copernik.eu> wrote:
>
> Hi Matt,
>
> On 2.12.2024 19:26, Matt Sicker wrote:
>> Seems like it might be useful to include the 2.x dependencies in the 3.x bom file then?
>
> They are already there: https://mvnrepository.com/artifact/org.apache.logging.log4j/log4j-bom/3.0.0-beta3
>
> Piotr
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: There is no log4j-slf4j2-impl in 3.0.0-beta3
Posted by "Piotr P. Karwasz" <pi...@mailing.copernik.eu>.
Hi Matt,
On 2.12.2024 19:26, Matt Sicker wrote:
> Seems like it might be useful to include the 2.x dependencies in the 3.x bom file then?
They are already there:
https://mvnrepository.com/artifact/org.apache.logging.log4j/log4j-bom/3.0.0-beta3
Piotr
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: There is no log4j-slf4j2-impl in 3.0.0-beta3
Posted by Matt Sicker <ma...@musigma.org>.
Seems like it might be useful to include the 2.x dependencies in the 3.x bom file then?
> On Nov 28, 2024, at 07:40, Piotr P. Karwasz <pi...@mailing.copernik.eu> wrote:
>
> Hi Pavel,
>
> On 28.11.2024 13:47, PavelTurk wrote:
>> 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?
>>
> In January this year we decided not to continue the development of Log4j API 3.
>
> The reason for this decision is simple: for a logging API it is unrealistic to assume that users can move all their code and dependencies from Log4j API 2 to Log4j API 3 at once. If we want breaking changes in Log4j API 3, we have two choices:
>
> 1. We can use a new package name. For me this means: introduce yet another logging API.
>
> 2. We can make no breaking changes.
>
> We chose the second, so we decided we might as well call it Log4j API 2 and stress the independence of the API from the implementations. SLF4J has one native implementation, Log4j API 2 will soon have two (Log4j Core 2 and Log4j Core 3).
>
> Regarding version 2:
>
> * Both Log4j API 2 and Log4j Core 2 will be supported for a long time.
>
> * Log4j API 2 will be actively developed for the foreseeable future. This means: at least until we find a successor. Personally I would like the next logging API to be developed in collaboration between multiple implementers and users, so we can stop this logging API war that has been going on for years. An external standardization body that guarantees to maintain the API after we all retire would be ideal for this purpose. Together with Christian and Volkan we reached out to Jakarta[2], but judging from the answers, a Jakarta Logging API is unlikely to appear.
>
> * We didn't discuss the details yet, but Log4j Core 2 might switch to "bug-fixes only" and then to "security-fixes only" some time after the first 3.0.0 release.
>
> Piotr
>
> [1] https://lists.apache.org/thread/p2lgr3xtt9hq77j7r67r8x1tc1z7kbol
>
> [2] https://www.eclipse.org/lists/jakarta.ee-spec/msg03511.html
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: There is no log4j-slf4j2-impl in 3.0.0-beta3
Posted by "Piotr P. Karwasz" <pi...@mailing.copernik.eu>.
Hi Pavel,
On 28.11.2024 13:47, PavelTurk wrote:
> 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?
>
In January this year we decided not to continue the development of Log4j
API 3.
The reason for this decision is simple: for a logging API it is
unrealistic to assume that users can move all their code and
dependencies from Log4j API 2 to Log4j API 3 at once. If we want
breaking changes in Log4j API 3, we have two choices:
1. We can use a new package name. For me this means: introduce yet
another logging API.
2. We can make no breaking changes.
We chose the second, so we decided we might as well call it Log4j API 2
and stress the independence of the API from the implementations. SLF4J
has one native implementation, Log4j API 2 will soon have two (Log4j
Core 2 and Log4j Core 3).
Regarding version 2:
* Both Log4j API 2 and Log4j Core 2 will be supported for a long time.
* Log4j API 2 will be actively developed for the foreseeable future.
This means: at least until we find a successor. Personally I would like
the next logging API to be developed in collaboration between multiple
implementers and users, so we can stop this logging API war that has
been going on for years. An external standardization body that
guarantees to maintain the API after we all retire would be ideal for
this purpose. Together with Christian and Volkan we reached out to
Jakarta[2], but judging from the answers, a Jakarta Logging API is
unlikely to appear.
* We didn't discuss the details yet, but Log4j Core 2 might switch to
"bug-fixes only" and then to "security-fixes only" some time after the
first 3.0.0 release.
Piotr
[1] https://lists.apache.org/thread/p2lgr3xtt9hq77j7r67r8x1tc1z7kbol
[2] https://www.eclipse.org/lists/jakarta.ee-spec/msg03511.html
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: There is no log4j-slf4j2-impl in 3.0.0-beta3
Posted by PavelTurk <pa...@gmail.com>.
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-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: There is no log4j-slf4j2-impl in 3.0.0-beta3
Posted by "Piotr P. Karwasz" <pi...@mailing.copernik.eu>.
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-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org