groovy-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul King (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GROOVY-8520) Replace commons-cli with picocli in CliBuilder
Date Fri, 13 Apr 2018 10:55:00 GMT

    [ https://issues.apache.org/jira/browse/GROOVY-8520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16437173#comment-16437173
] 

Paul King commented on GROOVY-8520:
-----------------------------------

I have been playing around seeing if I could carve out a mini cli SPI, see the {{CliParser}}
interface in this outdated PR in the old Groovy repo:
https://github.com/groovy/groovy-core/pull/414/files

The idea being to make it much easier to switch our cli backend using the service provider
mechanism.
My conclusion is that it isn't worth it. What I'll do now is instead create a groovy-cli module
and probably a groovy-cli-commons module.
I would expect your patch would mostly move into a groovy-cli-picocli module. But give me
a bit more time to progress my current spike.
Long-story short: there will be one groovy.util.CliBuilder and one with a longer package name.
We can make an assessment on compatibility to determine which gets the tick for the short
name.

Wrt your questions above, I have kind of lost track of outstanding issues but given what I
am planning with keeping both versions around, I am not too concerned. However, it might be
useful if you can summarise the status. You mentioned just one failing test (that doesn't
seem like a show-stopper to me) but should I assume the ones ear-marked as "invalid" are still
not catered for in some sense? And are the "behavioral changes" still in play?

> Replace commons-cli with picocli in CliBuilder
> ----------------------------------------------
>
>                 Key: GROOVY-8520
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8520
>             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|https://lists.apache.org/thread.html/d60b6d5d4411e9ba0d7dc209cde8a9bb4abb00f0b9c0322f068c322e@%3Cdev.groovy.apache.org%3E]
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
(v7.6.3#76005)

Mime
View raw message