arshadmohammad edited a comment on pull request #1637: URL: https://github.com/apache/zookeeper/pull/1637#issuecomment-796897813
> I believe we must drop log4j1 soon, because it is EOL and unsupported and it has a few CVS. > So the short term plan is to remove it at all AFAIK, moving to log4j2 is in discussion from long time but for one or other reasons getting stuck. This change i have tried to make it very independent, there is only one line change in main zookeeper code. So whenever the migration log4j2 happens this feature can be easily removed also these capabilities are already there in log4j2. There will not need to have this at all. anyway we have to remove. But until migration to log4j2 happens ,can we keep this? What you suggest? ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
