GROOVY-6675 : Base script support for JCommander annotation-based parameters #371
Conversation
…notation support them as well.
…ptJCommander that the script declares as a field.
|
Refined API for multiple command dispatching and many other fussy details to cover every possible initialization scenario. Also a goodly dose of Javadoc. A blog post or somesuch will be forthcoming. Note also that since this version now lives in |
|
Hi Jim! Could you give us a bit of status update wrt to this PR and the associated tickets? Is that ready for merge? |
|
I expect that the PR is out-of-date by now, especially since Paul did some work on 6624 which needs to be merged with this. I should be able to get current with master and update the PR on Monday or Tuesday. |
…ds are called Subcommand now and exit codes are handled.
|
I take that back. Looks like 6624 has more work to do and the lights are still green here. I've merged a couple tweaks from using this in Gondor development. It's all good to go from my perspective. |
…roovy#433) Fixes or partially addresses the following: GROOVY-6699: ignore properties/fields during serialization GROOVY-6854: serialize ISO-8601 dates GROOVY-6975: deactivate unicode escaping GROOVY-7682: JodaTime/JSR310 (using custom converter) GROOVY-7780: exclude null values
As the jira explains [http://jira.codehaus.org/browse/GROOVY-6675], we need a base script in Groovy to support super cool declarative scripts that use annotations to define the argument parsing into parameters. The base script is
groovy.cli.JCommanderScriptwhich provides JCommander annotations which we use because Apache CLI doesn't have any yet. JCommander is already in Groovy because of TestNG so we put this class there so that it doesn't change anything for folks that don't have/want JCommander.This PR also bumps TestNG to 6.8.8 and JCommander to 1.35.