Jan de Gorter

Can this issue be closed and/or is the behavior like the testCase below expected? I upgraded from JCommander 1.72 to 1.78 and encountered a change which looks like it is...

Same Issue with IntelliJ I only have the following VM options: --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED Clearly the above does not...

I have the same problem. After upgrading from older version to 18.09.1 containers that were running up to the moment the system is rebooted are **not** started after system reboot....