[
https://issues.apache.org/jira/browse/LOG4J2-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16125917#comment-16125917
]
ASF subversion and git services commented on LOG4J2-2011:
---------------------------------------------------------
Commit 0007b107b94f5b5024ea4aaa189bb8e0b7bf1c5c in logging-log4j-tools's branch
refs/heads/master from rpopma
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j-tools.git;h=0007b10 ]
LOG4J2-2011 replace JCommander command line parser with picocli to let users
run Log4j2 utility applications without requiring an external dependency
> replace JCommander with picocli
> -------------------------------
>
> Key: LOG4J2-2011
> URL: https://issues.apache.org/jira/browse/LOG4J2-2011
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core, Servers
> Affects Versions: 2.8.2
> Reporter: Remko Popma
> Assignee: Remko Popma
> Fix For: 2.9
>
>
> As discussed in the mailing list, replace uses of JCommander with
> [picocli|https://github.com/remkop/picocli] to get
> * customizable usage help
> * usage help with ANSI colors
> * better support for positional parameters (so we can use positional
> parameters for mandatory arguments and options for optional arguments)
> * include picocli as source so users can run these applications without
> requiring an external dependency
> Candidates for usage are:
> *log4j-core*
> * CustomLoggerGenerator
> * ExtendedLoggerGenerator
> * Generate
> * PluginManager
> *log4j-jmx-gui*
> * ClientGui
> *log4j-1.2-api*
> * Log4j1ConfigurationConverter
> *logging-log4j-tools/log4j-server*
> * AbstractSocketServer
> * TcpSocketServer
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
