[slf4j-dev] slf4j 2.0.0-alpha6 still referring to log4j 1.x

[Ceki Gülcü]

Ralph,

If I remember correctly, you lobbied for LocationAwareLogger to admit an
additional Object[] parameter. This change was made in SLF4J version 1.6
at your behest. This broke backward compatibility with 1.5 bindings.
This was the only time backward compatibility was broken between 1.0 and
1.7, or in over 15 years.

It is rather ironic that you should imply on this mailing list that
SLF4J does not care about backward compatibility.

On another register, reload4j 1.2.18.2 fixed the log4j 1.x CVEs you
published recently. It was quite nice of you to file them. Thank you so
much. So, as of 1.2.18.2 Vijay has the option to use reload4j as an
alternative to log4j{1,2}.

Best regards,
-- 
Ceki Gülcü

Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch

On 1/23/2022 7:10 PM, Ralph Goers wrote:
> Support for SLF4J is provided by Log4j 2. However, support for 2.0.0-*
> has not yet been implemented because a) AFAIK SLF4J-511 has still not
> been fixed so it isn’t possible to get the fluent api to have correct
> location information and b) Ceki is known to change things that affect
> compatibility of implementations in alpha and beta releases since alpha
> and beta releases aren’t guaranteed to be production ready by definition.
> 
> Ralph
> 
>> On Jan 21, 2022, at 7:03 AM, Vijayendhiran M
>> <vijayendhiran.m at globallogic.com
>> <mailto:vijayendhiran.m at globallogic.com>> wrote:
>>
>> Hi Team,
>>
>>  
>>
>> We are trying to upgrade slf4j to the latest version 2.0.0-alpha6
>> <https://mvnrepository.com/artifact/org.slf4j/slf4j-api/2.0.0-alpha6>.
>> We have noticed that it is still referring to log4j 1.x. We need to
>> upgrade log4j version 2.x in our application. Looking for your support.
>>
>>  
>>
>> Thanks,
>> Vijay.