[ 
https://issues.apache.org/jira/browse/LOG4J2-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519567#comment-17519567
 ] 

Gary D. Gregory commented on LOG4J2-3467:
-----------------------------------------

[~pkarwasz] 

TL;DR: Please, no.

I would say that the goal for log4j-1.2-api had to change since log4shell was 
released: We need to provide as close to possible a drop in replacement with 
this support improving with each release. I really am not a fan of yet more 
system properties, especially for the 1.2 compatibility layer. It's unfortunate 
that the module is called log4j-1.2-api instead of log4j-1.2-bridge or 
somesuch. The nature of 1.2, the use cases, the apps, built over years and 
years, which mixes API and implementation, all make it impossible IMO to 
practically offer reasonable compatibility without filling in implementations 
for the configuration APIs which all the apps I work on used for example.

> Update from Log4J 2.17.1 to 2.17.2 breaks application
> -----------------------------------------------------
>
>                 Key: LOG4J2-3467
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3467
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.17.2
>            Reporter: Alexander Veit
>            Priority: Major
>
> We have an application that uses a third-party library which seems to 
> reconfigure Log4J according to its needs. This worked for quite some years 
> with various Log4J versions.
> After upgrading from Log4J 2.17.1 to 2.17.2 a call to the library immediately 
> stops logging completely in the sense that no further logging is performed 
> until restarting the JVM.
> We've tried to identify the change that leads to the problem. Our best guess 
> is PropertyConfigurator, line 164 in
> https://github.com/apache/logging-log4j2/commit/73a2cd1cd0e94c7f4f36e4ac9dc72380d30750ef#diff-607596a6cadd10faf2dbeefc4e03092264b8e0dbe23fb89ffa6505d644602c9dR164
> Note that according to semantic versioning such breaking changes should not 
> occur when only the patch version is incremented. ;-)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to