Remko Popma

Current thinking is to generate a subclass that can get/set protected or package-private fields and methods in the annotated superclass. This is a reasonable restriction that is more maintainable than...

Hi @kristofdho I am not currently working on this and I don't see myself working on this in the near future. So I cannot give any estimate. However, this message...

@kristofdho Reflection happens at two times: * at initialization time to create the model (the hierarchy of `CommandSpec`, `OptionSpec` etc instances) * during parsing (`parseArgs`), after options and positional parameters...

@mikehearn That is a good question. I personally have not spent time profiling. I believe some others have, notably here: https://github.com/remkop/picocli/issues/1377 > (...) comment above saying that even with compile-time...

Sorry for my late response. ~~If you need to combine inheritance with mixins, then one idea would be to de-normalize the mixins:~~ * ~~move `@Option`-annotated fields out of the mixin...

Oops. I did not think that through... 😅 The above solution will still throw a duplication option error... Sorry about that. Take 2. The duplicate option error arises because the...

Looking at https://www.baeldung.com/spring-boot-command-line-arguments, it seems that Spring may **already be doing this** automatically. The Spring example in the picocli user manual starts the application as follows: ```java public static void...

@AlexandreCassagne Can you let me know your thoughts on this?

> However, it implies that some of the facilities offered by PicoCLI's argument parser (e.g. use of properties files, use of interactive arguments, …) are not available. Good point. Yes,...

@AlexandreCassagne What shall we do with this ticket? The documentation currently has a TIP section at the end of the [Spring Boot Example](https://picocli.info/#_spring_boot_example) that mentions defining a `--spring.config.location` option to...