Ruud Senden

Alternatively, we could look into the ability to also specify command name through mixins, and not requiring a `Command` annotation with `name` attribute on command classes. Not sure though whether...

Just had a further look at this, looks like auto-complete and man page generators just create a new `CommandLine` object that indirectly uses `CommandReflection::extractCommandSpec`, so updating that method as described...

@remkop Any suggestions on how to best implement this feature? This would really be of big benefit to our CLI application to ensure consistent command names and aliases. For example,...

This seems to be somewhat related to the following block in `build.gradle`: ``` micronaut { testRuntime("junit5") processing { incremental(true) annotations("org.sample.micronaut.*") } } ``` The `annotations` option in combination with our...

@remkop, some new information on this issue: * `ReflectionConfigGenerator::generateReflectionConfig` seems to generate the correct `reflect-config.json` (currently invoking this from a unit test in the main application module that has all...

Both clean and incremental builds show the same behavior. We normally build native binaries only from our GitHub Actions workflow, with a clean workspace, and the missing `reflect-config.json` entries cause...

@remkop Thanks for the notice, we'll look into finding a solution and raising a PR for this issue as time allows.

I think most Markdown implementations consider text that's indented with a certain number of spaces as code blocks, but most implementations require an empty line before and after the code...

Hi @remkop, given our current codebase, support for custom annotations probably wouldn't provide much value anymore. However, it would still be useful if command name could be defined through a...

@remkop It looks like ArgGroups are causing this issue, and setting `defaultValue` to `Option.NULL_VALUE` indeed helps to remediate this issue. Tested with picocli 4.7.4, the code below results in the...