Grzegorz Kowal - 2018-02-20

This is a bit tricky. Launch4j uses only arguments with --l4j- prefix, otherwise your application would not be able to display a help itself if -h and --help were intercepted by the wrapper. Also when trying to figure out the version of a console program I'd would not expect to see the version of a wraping tool but the program itself. Therefor the version is logged when --l4j-debug is used.

You say that the end users are lost when something goes wrong... But for this kind of situation you have the possibility to customize launch4j error messages to better explain what went wrong. Additionally you can set the support URL, where a website can be opened in case of error. This was meant to open your website where you could explain how to proceed and provide some information or specific requirements. Have you tried that?

The problem with opening launch4j documentation is that if I was to run a program wrapped using launch4j and an error occurred I wouldn't have the slightest idea what to do with that information or even what that tool is. For me it would be suspicious to see a website telling me to execute things when I have never downloaded the program and I don't know what it is. That's why the idea was to open your website.

The hint to use --l4j-debug can be done by customizing the error messages, so it's purely configuration.

The runtime options could be listed in fact but this should not interfere with the wrapped program output, so it could be triggered for example by --l4j-help or something like that.

Best regards,
Grzegorz