Mr. Grun,
Good news on my end!
The revised installation BaseX Windows installation was very helpful. It showed the following:
--------------------------- BaseX Setup --------------------------- Please install Java 11 or higher before executing the installer. Analyzed Java version string: java version "1.6.0" Java(TM) SE Runtime Environment (build pwi3260sr9fp1-20110208_03(SR9 FP1)) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows Vista x86-32 jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) J9VM - 20110203_074623 JIT - r9_20101028_17488ifx3 GC - 20101027_AA) JCL - 20110203_01 --------------------------- OK ---------------------------
I went to Control Panel, and sure enough, it showed two Java installations: 1) Eclipse Temurin JRE with Hotspot 17.0.8.1+1 (x64) 2) IBM 32-bit Runtime Environment v6
I uninstalled the IBM's Java v6, and successfully installed the latest BaseX 11.0 beta build c21851a!!!
There are still some questions remaining. Where and how BaseX installer got into old Java v1.6 and missed a legitimate Eclipse Temurin JRE with Hotspot 17.0.8.1+1?
c:>java -version shows the following openjdk version "17.0.8.1" 2023-08-24 OpenJDK Runtime Environment Temurin-17.0.8.1+1 (build 17.0.8.1+1) OpenJDK 64-Bit Server VM Temurin-17.0.8.1+1 (build 17.0.8.1+1, mixed mode, sharing)
c:>path shows the following: PATH=C:\Program Files\Eclipse Adoptium\jre-17.0.8.101-hotspot\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOW S\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WI NDOWS\System32\OpenSSH;C:\Windows\CCM;C:\Program Files\Eclypsium;C:\Program Files (x86)\Microsoft SQL Server\160\DTS\Binn;C:\Program Files\Azure Data Studio\bin;C:\Users\i300179\AppData\Local\Microsoft\WindowsApps;
Overall, that's a lot for such a great support of the product.
Regards, Yitzhak Khabinsky
Where and how BaseX installer got into old Java v1.6 and missed a legitimate Eclipse Temurin JRE with Hotspot 17.0.8.1+1?
Good question. We would need to better understand the NSIS installer code [1]. The installer provided dedicated Java checks, but those did not work with newer JDK versions anymore, which is why we switched to the basic 'java -version' call.
If someone has worked with NSIS in the past, feel free to share your knowledge.
[1] https://nsis.sourceforge.io/Main_Page
c:>java -version shows the following openjdk version "17.0.8.1" 2023-08-24 OpenJDK Runtime Environment Temurin-17.0.8.1+1 (build 17.0.8.1+1) OpenJDK 64-Bit Server VM Temurin-17.0.8.1+1 (build 17.0.8.1+1, mixed mode, sharing)
c:>path shows the following: PATH=C:\Program Files\Eclipse
Adoptium\jre-17.0.8.101-hotspot\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOW S\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WI NDOWS\System32\OpenSSH;C:\Windows\CCM;C:\Program Files\Eclypsium;C:\Program Files (x86)\Microsoft SQL Server\160\DTS\Binn;C:\Program Files\Azure Data Studio\bin;C:\Users\i300179\AppData\Local\Microsoft\WindowsApps;
Overall, that's a lot for such a great support of the product.
Regards, Yitzhak Khabinsky
basex-talk@mailman.uni-konstanz.de