[
https://issues.apache.org/jira/browse/ZOOKEEPER-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17576684#comment-17576684
]
Brahma Reddy Battula commented on ZOOKEEPER-4427:
-------------------------------------------------
won't it be incompatible (who migrates from branch-3.6,3.7 and 3.5 to 3.8)..? I
think, we can use reload4j which is fully incompatible. Even branch-3.7,3.6 and
3.5 uses the same.?
> Migrate to Logback
> ------------------
>
> Key: ZOOKEEPER-4427
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4427
> Project: ZooKeeper
> Issue Type: Improvement
> Components: other
> Affects Versions: 3.8.0
> Reporter: Andor Molnar
> Assignee: Andor Molnar
> Priority: Major
> Labels: log4j, logback, logging, pull-request-available
> Fix For: 3.8.0
>
> Time Spent: 7h
> Remaining Estimate: 0h
>
> Due to the recent issues with log4j2 the migration for another logging
> library has come up again. Although log4j1 is not impacted by the
> vulnerability, the upgrade to log4j2 was abandoned multiple times in ZK
> history.
> I suggest now to migrate to {{logback}} which is also a well-maintained and
> mature project as well as it's much easier to migrate from log4j1.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
