anchor.diff:  `DynamicProxyConfigGenerator` generates a JSON String with the fully qualified interface names for which
   dynamic proxy classes should be generated at native image build time.
   
  +The <<Generate Documentation,generated>> manual page for the `DynamicProxyConfigGenerator` tool https://picocli.info/man/gen-proxy-config.html[is here].
  +
   The output of `DynamicProxyConfigGenerator` is intended to be passed to the `-H:DynamicProxyConfigurationFiles=/path/to/proxy-config.json` option of the `native-image` GraalVM utility,
   or placed in a `META-INF/native-image/` subdirectory of the JAR.
   
  
positive.code: and it needs to know ahead of time the reflectively accessed program elements.
  
  `ReflectionConfigGenerator` generates a JSON String with the program elements that will be accessed reflectively in a picocli-based application, in order to compile this application ahead-of-time into a native executable with GraalVM.
  
  The output of `ReflectionConfigGenerator` is intended to be passed to the `-H:ReflectionConfigurationFiles=/path/to/reflect-config.json` option of the `native-image` GraalVM utility,
  or placed in a `META-INF/native-image/` subdirectory of the JAR. 
  
negative.code: `ResourceConfigGenerator` generates a JSON String with the resource bundles and other classpath resources
  that should be included in the Substrate VM native image.
  
  The <<Generate Documentation,generated>> manual page for the `ResourceConfigGenerator` tool https://picocli.info/man/gen-resource-config.html[is here].
  
  The output of `ResourceConfigGenerator` is intended to be passed to the `-H:ResourceConfigurationFiles=/path/to/reflect-config.json` option of the `native-image` GraalVM utility,
  or placed in a `META-INF/native-image/` subdirectory of the JAR. 
  
  