Azul / OpenJDK integration
Brought to you by:
grzegok
Menu
▾
▴
https://www.azul.com/products/zulu/
We are having the same problem here, using Keystore Explorer in connection with OpenJDK (Zulu 64-bit, Windows), see also https://github.com/kaikramer/keystore-explorer/issues/52.
I suppose the link is https://github.com/kaikramer/keystore-explorer/issues/52 (without a dot at the end)
The dot is orthography, i.e. the end lf a sentence. What SF makes of it is just bad auto-formatting.
Given all that's happened recently with Oracle and the JRE licensing, I believe this feature improvement will be of great value to many users.
I had a quick look at the code, and it appears that it might just need the addition of another registry search location (certainly for zulu). However not a C/C++ coder, so wasn't sure if i'm missing something.
OpenJDK would be harder as there's no installer, so could be anywhere on the PATH, and it appears launch4j doesn't search the PATH for candidates - maybe this could also be a feature request.
Either that or an option to disable the check if you have the bundler JRE.
Last edit: Javier Ortiz 2018-12-02
Any progress here? Same issue with AdoptOpenJDK.
Please have a look at https://sourceforge.net/p/launch4j/feature-requests/127/
It's not a registry search but also some improvement in case of Adopt which is not registered.
Last edit: Grzegorz Kowal 2019-03-13
Zulu does write to the registry, but it has 2 different behaviours.
If Oracle Java is installed then Zulu writes to it's own locations. If Oracle Java is not installed, then Zulu writes to it's own locations AND the traditional Oracle ones.
In this second case launch4j picks it up without any further changes. However in the former case (which we believe will be very common) then Zulu is not selected.
By default Zulu installer doesn't add itself to the PATH.
I'm a bit surprised the JAVA_HOME environment variable is not examined first by default. That would fix issues for AdoptOpenJDK.