Hi Ralph,
On Mon, 22 Apr 2024 at 03:35, Ralph Goers wrote:
>
> Did we make a decision on this?
Since apparently there is consensus in the PMC, I opened an issue[1]
and I am going to remove `log4j-1.2-api` from the `main` branch.
Piotr
[1] https://github.com/apache/logging-log4j2/issues/2461
Did we make a decision on this?
Ralph
> On Apr 8, 2024, at 4:02 PM, Ralph Goers wrote:
>
>
>
>> On Apr 8, 2024, at 2:40 PM, Jochen Wiedmann
>> wrote:
>>
>> On Mon, Apr 8, 2024 at 1:11 PM Apache wrote:
>>
>>> My opinion is to drop it from 3.0.0. 2.x is going to live a long time
>>>
> On Apr 8, 2024, at 2:40 PM, Jochen Wiedmann wrote:
>
> On Mon, Apr 8, 2024 at 1:11 PM Apache wrote:
>
>> My opinion is to drop it from 3.0.0. 2.x is going to live a long time still.
>> By the time it dies Log4J 1.x will have been dead well over 15 years, maybe
>> even 20. That would
On Mon, Apr 8, 2024 at 1:11 PM Apache wrote:
> My opinion is to drop it from 3.0.0. 2.x is going to live a long time still.
> By the time it dies Log4J 1.x will have been dead well over 15 years, maybe
> even 20. That would give users plenty of time to be aware that they need to
> plan to
Agreed with Ralph.
I second the idea of dropping `log4j-1.2-api` from `3.0.0`.
On Mon, Apr 8, 2024 at 1:11 PM Apache wrote:
> My opinion is to drop it from 3.0.0. 2.x is going to live a long time
> still. By the time it dies Log4J 1.x will have been dead well over 15
> years, maybe even 20.
My opinion is to drop it from 3.0.0. 2.x is going to live a long time still. By
the time it dies Log4J 1.x will have been dead well over 15 years, maybe even
20. That would give users plenty of time to be aware that they need to plan to
upgrade.
Ralph
> On Apr 8, 2024, at 3:35 AM, Piotr P.
Hi all,
As you are probably aware, `log4j-1.2-api` is the second largest
artifact we maintain. Yes, it is slightly larger than `log4j-api` and
twice the size of JTL.
This library is mainly used:
1. By some older frameworks/libraries that want to "help" users in
their logging configuration. The
