MartijnVisser commented on PR #29120:
URL: https://github.com/apache/flink/pull/29120#issuecomment-5801269230

   @piotrp Thanks, both are fixed. Since this breaks existing setups, I think 
we need agreement on dev@ before it goes into a minor release. Can you start a 
[DISCUSS] thread? It should cover that in each of these cases the logs are 
silently gone:
   
   - projects created from our quickstart archetype, until `log4j-slf4j-impl` 
is replaced by `log4j-slf4j2-impl`
   - clusters running Logback 1.2 or Log4j 1
   - jars in `lib/` that bundle `slf4j-api` 1.x
   - connectors that pin SLF4J 1.7, once they build against 2.4
   
   And the question whether we do this in 2.4 or wait for 3.0. 1.11 switched to 
Log4j 2 in a minor release too, but without breaking backwards compatibility: 
Log4j 1 kept working. The CVEs in Logback 1.2 are the main argument for 2.4.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to