groovy-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pascal Schumacher (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (GROOVY-4419) CliBuilder formatting improvements
Date Sun, 05 Jul 2015 13:57:04 GMT

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

Pascal Schumacher closed GROOVY-4419.
-------------------------------------
    Resolution: Incomplete

I'm closing this, because Pauls question was never answered.

> CliBuilder formatting improvements
> ----------------------------------
>
>                 Key: GROOVY-4419
>                 URL: https://issues.apache.org/jira/browse/GROOVY-4419
>             Project: Groovy
>          Issue Type: New Feature
>          Components: command line processing
>            Reporter: Jonathan Felch
>            Priority: Trivial
>
> My organization has specific standards for --help messages, usage instructions and such.
 Very UNIX-y, very Close to what CliBuilder give you out of the box.  So this is a general
appeal to give the user more opportunity to customize the output with a few specific requests.
 
> When you type XXX --help for any command that has a non-existent option.  You get the
error: ParseException.message before the usage() message.  First, our norm is a blank line
between the error message and the usage message, which I can't do because of the way parse(args)
is written.  Adding a blank line would be good.  Adding a public string that lets you specify
error handing would be good.  Placing the exception handler in a closure and letting the user
over-ride error conditions might also work. 
> Second, the parse exception should probably be handled differently when the only option
passed is --help.  This may be more of an issue for how Commons CLI handles their exception
policy and thus rightly belong to them, but CliBuilder's genius is that is make Apache CLI
workable, so you might think about it anyways.  
> Lastly, we have introduced Groovy UNIX shell scripts into an org where Python and PERL
dominate the scripting world and scheduled scripts are important to our business, so the combo
of the CliBuilder and shell scripting support has made Groovy and the JVM relevant in a way
this organization would never have imagined a few years ago. 



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

Mime
View raw message