anchor.diff:  From picocli 3.0, applications can call `CommandLine.setPosixClusteredShortOptionsAllowed(false)` to enforce that options must be separated with whitespace on the command line.
   (This also means that option parameters must be separated from the option name by whitespace or the `=` <<Option-Parameter Separators,separator>> character, so `-D key=value` and `-D=key=value` will be recognized but `-Dkey=value` will not.)
   
  -=== Lenient Mode (Incubating)
  +=== Lenient Mode
   From picocli 3.2, the parser can be configured to continue parsing invalid input to the end.
   When `collectErrors` is set to `true`, and a problem occurs during parsing, an `Exception` is added to the `ParseResult.errors()` list and parsing continues. The default behaviour (when `collectErrors` is `false`) is to abort parsing by throwing the `Exception`.
   
  
positive.code: === Options
  An option must have one or more `names`.
  Picocli lets you use any option name you want.
  
  TIP: You may be interested in this http://catb.org/~esr/writings/taoup/html/ch10s05.html#id2948149[list of common option names]. Following these conventions may make your application more intuitive to use for experienced users.
  
  
negative.code: public class Git { ... }
  ----
  
  Subcommands referenced in a `subcommands` attribute _must_ have a `@Command` annotation with a `name` attribute, or an exception is thrown from the `CommandLine` constructor.
  This name will be used both for generating usage help and for recognizing subcommands when parsing the command line.
  Command names are case-sensitive by default, but this is <<Case Sensitivity,customizable>>.
  
  Custom type converters registered on a `CommandLine` instance will apply to all subcommands that were declared on the main command with the `subcommands` annotation.
  
  