In continuing to debug this issue and we reviewed the Amazon Corretto Java 11 source code. We understand the platform encoding exception as shown in my previous comment to you, but don't know exactly what issues Jar2EXE is having using the instructed JRE. We have always used the /config "jre_order b" configuration and placed a JRE in the same folder next to your generated executable named "jre". We tried the /config "jre_order c" and pointed directly to the JVM DLL. We've tried /config "export PATH=" to clear the path as you instructed to the other individual on this thread. All to no avail.
It appears as though if the PATH has any other JRE's, Jar2EXE simply fails to properly initialize. Being that we've said to use the specific JRE by way of /config "jre_order b" to use the bundled JRE (as we have for years), it should be enough. Additionally, we've tried the config options:
/config "export PATH="
/config "export PATH=./jre/bin"
/config "export PATH=/jre/bin"
but it seems as though Jar2EXE simply is not honoring these. Wtih all of this being said, do you have any other suggestions or a timeline on an updated version of Jar2EXE that addresses this issue?
Hello,
In continuing to debug this issue and we reviewed the Amazon Corretto Java 11 source code. We understand the platform encoding exception as shown in my previous comment to you, but don't know exactly what issues Jar2EXE is having using the instructed JRE. We have always used the /config "jre_order b" configuration and placed a JRE in the same folder next to your generated executable named "jre". We tried the /config "jre_order c" and pointed directly to the JVM DLL. We've tried /config "export PATH=" to clear the path as you instructed to the other individual on this thread. All to no avail.
It appears as though if the PATH has any other JRE's, Jar2EXE simply fails to properly initialize. Being that we've said to use the specific JRE by way of /config "jre_order b" to use the bundled JRE (as we have for years), it should be enough. Additionally, we've tried the config options:
/config "export PATH="
/config "export PATH=./jre/bin"
/config "export PATH=/jre/bin"
but it seems as though Jar2EXE simply is not honoring these. Wtih all of this being said, do you have any other suggestions or a timeline on an updated version of Jar2EXE that addresses this issue?
Thank you for your time!
Joey Prevo