picocli in log4j

Thanks all for your positive feedback on picocli back in April. There have been multiple releases since then and I am confident about its stability now. Any objections if I replace our current usage of JCommander with picocli? Main benefits: - C

[jira] [Commented] (LOG4J2-1922) SocketHandler leaks connection if EOFException is thrown

[ https://issues.apache.org/jira/browse/LOG4J2-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114480#comment-16114480 ] Gary Gregory commented on LOG4J2-1922: -- I adjusted the Javadocs and CLI to document

[jira] [Commented] (LOG4J2-1997) Test classes do not close resources and use deprecated methods

[ https://issues.apache.org/jira/browse/LOG4J2-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114091#comment-16114091 ] ASF GitHub Bot commented on LOG4J2-1997: GitHub user kpm1985 opened a pull reques

[GitHub] logging-log4j2 pull request #106: LOG4J2-1997 This cleans up the entire test...

GitHub user kpm1985 opened a pull request: https://github.com/apache/logging-log4j2/pull/106 LOG4J2-1997 This cleans up the entire test package of import wildcards… …, deprecated methods, typos and other trivial issues. You can merge this pull request into a Git repository by ru