But I don't use JNI. I'm using the default (old) method...
The JNI error is thrown with two GUI dialogs popping up, plus, at elast in launch4j, there's a stacktrace message, that indicates, that some classes are not found. That's why I guess, my classpath entry ./lib/* is a problem for launch4j without the "Changedir" . I also tried lib/*, but it would also only work with Changedir ..
This happens with 3.9 by the way...
EXE cannot be launched from launch4j or Java, but from Explorer when using relative classpath
The issue has been fixed upstream in version 2.0.2 of universalJavaApplicationStub. Sorry for the trouble and thanks for the contribution!
I'm sorry, I'm confused now. I would have expected that the download package "launch4j-3.9-macosx-x86-10.8.tgz"...
Thanks for the information, Thomas! Unfortunately the launch4j-maven-plugin still...
I'm using the package launch4j-3.9-macosx-x86.tgz on macOS 10.12.3 "Sierra"