vlsi commented on pull request #608: URL: https://github.com/apache/logging-log4j2/pull/608#issuecomment-993430513
I see a lot of comments that "log4j 1.x has reached its end of life". However, is there a chance there will be log4j 1.2.18 that just removes the offending features (e.g. JMSAppender, JmsSink, Chainsaw, SocketServer, SocketNode)? It just does not sound right that the only log4j team answer is "migrate to 2.x or try removing class files from jars". The issue is that log4j2 is not really a drop-in replacement for log4j1, and there are a lot of users that can't migrate because they would need to adjust their code and configuration files. Is there true maintenance overhead associated with removing certain classes from the source and removing the corresponding tests? -- 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]
