[ 
https://issues.apache.org/jira/browse/LOG4J2-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Remko Popma resolved LOG4J2-2011.
---------------------------------
    Resolution: Fixed

Migrated to picocli, and users no longer need an external dependency to run 
Log4j2 utility applications like TcpSocketServer or 
Log4j1ConfigurationConverter.

There is still some remaining work to add {{description}} annotations on these 
commands to generate nicer usage help messages, and migrate some other utility 
applications that did not use JCommander to use picocli.

> 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)

Reply via email to