Per

Sounds like a solution has been provided. Is there a planned release in the near future? This feature would be extremely helpful for us.

I agree, having a way to specify one specific exit code would be great (if there is no other way to trigger a restart-signal?) In our case we have additional VM parameters added to the l4j.ini file during startup when we do an "application update" and therefore would want a restart. Currently we display a notification that restart is needed which is less user friendly. Any workaround for this scenario?

Totally agree with Mc Solaar, having multiple <path> elements supported would be a great improvement. In our case we would probably do something like this:</path> <!-- search locally if we have bundled jdk 11 --> <path>jdk</path> <!--multiple java versions installed --> <path>%JAVA_11_HOME%</path> <!-- default if nothing else is found --> <path>%JAVA_HOME%</path>

AntumDeluge, I tried setting the <path> as you describe, but it does not seem to work with Oracle JDK 11 zip distribution. Is it possible to use environment variables in the jre <path> element?</path></path>

We have the same problem. People are downloading the ZIP distribution (java 11) from Oracle and from my understanding this does not work with Launch4j?? Is there any workaround for this at all? I suggest searching environment variable JAVA_11_HOME for java 11 as a fallback if nothing is found in the registry (and we have configured "min version = 11"). Can we point to a jdk/jre in the l4j.ini file? add something to PATH? Any workaround at all we can implement? I assume adding environment variable...