anchor.diff:  The `-x` argument "looks like" an option but there is no `-x` option defined...
   
   One possibility is to silently accept such values as positional parameters but this is often not desirable.
  -From version 1.0.0, picocli determines if the unmatched argument "looks like an option"
  +From version 1.0, picocli determines if the unmatched argument "looks like an option"
   by comparing its leading characters to the prefix characters of the known options.
   
   When the unmatched value is similar to the known options, picocli throws an `UnmatchedArgumentException`
  
positive.code: Subcommands added later will not have the converter added automatically.
  To ensure a custom type converter is available to all subcommands, register the type converter last, after adding subcommands.
  
  === Arrays, Collections, Maps
  
  IMPORTANT: With array fields picocli uses reflection to discover the array element type, but with collections,
  Java type erasure means picocli cannot find out the generic type of the collection.
  For non-String collections, use the `type` attribute to specify what type to convert the command line arguments to.
  
  ==== Arrays and Collections
  
  Multiple parameters can be captured together in a single array or `Collection` field. When using a collection, use the `type` attribute to specify the collection element type. For example:
  
  [source,java]
  ----
  
negative.code: However, picocli lets you make options required if you want to, see <<Required Arguments>>.
  
  == Tracing
  Picocli v1.0 introduced support for parser tracing to facilitate troubleshooting.
  
  System property `picocli.trace` controls the trace level. Supported levels are `OFF`, `WARN`, `INFO`, and `DEBUG`. The default trace level is `WARN`.
  
  