Markus KARG

@Param(default = )

1

When using complex parameter types, often the defaults printed by `usage()` are unreadable. For example, the class of the parameter does not overwrite `toString()` so it prints just a hash...

Multiple Default Providers

2

Sophisticated CLI tools allow the provision of multiple default sources, e. g. in a first step these tools will check environment variables, and if nothing found, they will check property...

Combining required=true with defaults

1

Currently required=true enforces the explicit provision of a parameter at the command line. In fact, it would be very useful, is a default would be considered, i. e. the error...

Maven Central Updates

6

I would be happy if jCommander 1.80 could be pushed to Maven Central. :-)

Support for default command

1

For some applications it might be beneficial to have a default command which will be invoked if no command is explicitly provided. Currently in this situation `usage()` is executed, but...

SubCommands

7

Some CLI utilities use multi-word commands alias "Sub Commands": `docker container list `. It would be great if JCommander would support the registration of sub commands with unlimited depth.

Apparently `IDefaultProvider` is invoked multiple times for the same parameter, once per each of its names, even in case an explicit value *is* given, i. e. when no default is...

It would be great if usage() would print an explanating text for the unnamed parameter as part of the parameter list. It confuses users that just options are explained, but...

It would be great if one could set a description not on the parameter level but also on the tool level itself, to print a short introduction of the tool...

Skipping execution if nothing was changed

2

**Feature Request** Please skip execution if nothing was changed. **What is the current behavior?** The plugin runs external processes, like npm or ng, even in case the source code or...