groovy-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul King (JIRA)" <>
Subject [jira] [Commented] (GROOVY-8520) Replace commons-cli with picocli in CliBuilder
Date Sat, 21 Apr 2018 07:25:00 GMT


Paul King commented on GROOVY-8520:

 For Groovy 3, neither will be in groovy.util to comply with Jdk9+ modules. The compiler will
map package names to retain source compatibility or we might try some class loader trick to
rename if that is still possible - haven't finished researching possible options.

For 2.5, I was leaning towards your first suggestion but wanted to do a bit more testing and
also see how we went with swapping over Groovy's native use of commons-cli.

Also, even with the separate groovy-cli-commons module commons-cli currently ends up on the
classpath for all tests. We need to make sure all that swaps over without error.

> Replace commons-cli with picocli in CliBuilder
> ----------------------------------------------
>                 Key: GROOVY-8520
>                 URL:
>             Project: Groovy
>          Issue Type: Improvement
>          Components: command line processing
>            Reporter: Remko Popma
>            Priority: Major
> This ticket proposes to replace commons-cli with picocli in {{groovy.util.CliBuilder}}.
> See [discussion on the mailing list|]
for the original proposal and comparison with other CLI libraries.
> Goals for the initial implementation:
> * preserve the current CliBuilder behaviour as much as possible
> * deliver an implementation, tests and documentation in time to be included in the 2.5
GA release

This message was sent by Atlassian JIRA

View raw message