groovy-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GROOVY-6675) Implement JCommander base script to support purely declarative script options
Date Wed, 29 Nov 2017 16:33:00 GMT

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

Remko Popma commented on GROOVY-6675:
-------------------------------------

[~paulk] Thanks! 
Paul, I know GROOVY-6090 is closed, but do you think there would any interest to integrate
picocli with CliBuilder so that all Groovy command line apps could have ANSI [color usage
help|http://picocli.info/#_ansi_colors_and_styles] out of the box (and, with some steps, [TAB
autocomplete|http://picocli.info/autocomplete.html])?

> Implement JCommander base script to support purely declarative script options
> -----------------------------------------------------------------------------
>
>                 Key: GROOVY-6675
>                 URL: https://issues.apache.org/jira/browse/GROOVY-6675
>             Project: Groovy
>          Issue Type: Improvement
>          Components: command line processing
>            Reporter: James P. White
>
> Implement the script base class org.codehaus.groovy.cli.JCommanderScript so that scripts
can have purely declarative (annotation defined) processing of command line options.
> Script base classes now support the wrapping of script bodies with arbitrary code (GROOVY-6585).
 That allows cool features like this.  For many purposes the base script does not need to
be in Groovy itself since there are Grapes.  But this one does because if specify the base
script class at the command line with the --basescript option (GROOVY-6615) then it must be
something already on the CLASSPATH.
> The bad news is that Apache CLI is still in the dark ages and does not have an annotation
scheme yet.  Groovy may eventually do something about that (GROOVY-6090), but that isn't happening
right now.  The good news is that Groovy does have JCommander by virtue of including TestNG.
 Therefore the solution is to put this class in the groovy-testng subproject for those who
want it.  Those who don't can safely ignore its existence.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message