This is an automated email from the ASF dual-hosted git repository.
cadonna pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/trunk by this push:
new 354a4e94708 Update note on upgrade from log4j to reload4j (#12164)
354a4e94708 is described below
commit 354a4e9470856763e98fdd7b28fb413faffd5805
Author: xjin-Confluent <[email protected]>
AuthorDate: Mon May 16 04:23:10 2022 -0700
Update note on upgrade from log4j to reload4j (#12164)
Reviewers: Nikhil Bhatia <[email protected]>, Bruno Cadonna
<[email protected]>
---
docs/upgrade.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/upgrade.html b/docs/upgrade.html
index 226013df8ca..0d7f98e3e04 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -72,7 +72,7 @@
Users can change this behavior to enable idempotence for some or
all producers
via Connect worker and/or connector configuration. Connect may
enable idempotent producers
by default in a future major release.</li>
- <li>Kafka has replaced log4j and slf4j-log4j12 with reload4j and
slf4j-reload4j due to security concerns.
+ <li>Kafka has replaced log4j with reload4j due to security concerns.
This only affects modules that specify a logging backend
(<code>connect-runtime</code> and <code>kafka-tools</code> are two such
examples).
A number of modules, including <code>kafka-clients</code>, leave
it to the application to specify the logging backend.
More information can be found at <a
href"https://reload4j.qos.ch";>reload4j</a>.
