[
https://issues.apache.org/jira/browse/KAFKA-9366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna updated KAFKA-9366:
-
Fix Version/s: 4.0.0
(was: 3.3.0)
> Upgrade log4j to log4j2
>
[
https://issues.apache.org/jira/browse/KAFKA-9366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna updated KAFKA-9366:
-
Fix Version/s: 3.3.0
(was: 3.2.0)
> Upgrade log4j to log4j2
>
[
https://issues.apache.org/jira/browse/KAFKA-9366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot updated KAFKA-9366:
---
Fix Version/s: (was: 3.1.0)
3.2.0
> Upgrade log4j to log4j2
>
[
https://issues.apache.org/jira/browse/KAFKA-9366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantine Karantasis updated KAFKA-9366:
--
Fix Version/s: (was: 3.0.0)
3.1.0
> Upgrade log4j to log
[
https://issues.apache.org/jira/browse/KAFKA-9366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantine Karantasis updated KAFKA-9366:
--
Fix Version/s: 3.0.0
> Upgrade log4j to log4j2
> ---
>
>
[
https://issues.apache.org/jira/browse/KAFKA-9366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dongjin Lee updated KAFKA-9366:
---
Summary: Upgrade log4j to log4j2 (was: please consider upgrade log4j to
log4j2 due to critical secur