You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (JIRA)" <ji...@apache.org> on 2015/06/07 10:32:00 UTC

[jira] [Assigned] (GROOVY-6090) Reimplement CliBuilder over another CLI API

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

Paul King reassigned GROOVY-6090:
---------------------------------

    Assignee: Paul King

> Reimplement CliBuilder over another CLI API
> -------------------------------------------
>
>                 Key: GROOVY-6090
>                 URL: https://issues.apache.org/jira/browse/GROOVY-6090
>             Project: Groovy
>          Issue Type: Wish
>          Components: command line processing
>    Affects Versions: 2.1.2
>            Reporter: Baruch Sadogursky
>            Assignee: Paul King
>            Priority: Minor
>
> current CliBuilder implementation is based on the dead and outdated commons-cli project, which affects its flexibility, API, design and fimits its features.
> There are better alternatives - commons-cli2, args4j, jcommander, to name a few.
> CLI processing is critical feature for Groovy scripts usability, and lacking in it drive people away (even devoted Groovy advocates like @russel_winder) and prevents adoption.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)