Remko Popma

Awesome, @volkov thank you for working on this! 👍 Will you be able to provide some unit tests?

Hi @volkov looks like you have made great progress! I took a brief look and I see you are also adding dejaGnu tests, much appreciated! I remember it took me...

Potentially related: https://github.com/remkop/picocli/issues/1804

@dkfellows You may have run into one of the limitations of the framework. One idea is to drop the use of Mixins and live with the duplication of the positional...

Note to self: as mentioned in https://github.com/SpiNNakerManchester/JavaSpiNNaker/pull/684, the issue is that under some circumstances positional parameters are sorted by arity.

I think this can be accomplished in the annotations. See: https://picocli.info/#_exception_exit_codes And https://picocli.info/apidocs-all/info.picocli/picocli/CommandLine.Command.html#exitCodeOnUsageHelp() ```java @Command(exitCodeOnUsageHelp = 42) class Cmd { //... ```

You may need to do this in the `@Command` annotation for the subcommands also...

Let's try to get a minimal example that reproduces the issue. This test passes for me. Does it pass for you? ```java import org.junit.jupiter.api.Test; import picocli.CommandLine; import static org.junit.jupiter.api.Assertions.assertEquals; public...

Okay, looking at your original code, I can see the answer: the code needs to call `System.exit` from the `main` method with the result of `CommandLine::execute`. I believe this will...

(By the way, picocli does not throw any checked exceptions, so I believe you can omit the try/catch from the main method.)