Install on windows fails because of JAVA_TOOL_OPTIONS
Monday, 10 February 2025 · 2 messages · last reply 22 Feb 2025
PB
Peter Boot10 Feb 2025 15:22 #
Hello,
I tried to install BaseX on Windows 11 and it kept giving me the message that Java 11 was needed, even though I already was at 20 and now am at 21.
Then I noticed that java --version also reported a JAVA_TOOLS_OPTIONS environment variable:
java --version
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
openjdk 21.0.6 2025-01-21 LTS
OpenJDK Runtime Environment Temurin-21.0.6+7 (build 21.0.6+7-LTS) OpenJDK 64-Bit Server VM Temurin-21.0.6+7 (build 21.0.6+7-LTS, mixed mode, sharing)
After removing that variable it no longer appears in the output of the version command and the install runs fine. I suppose it messes up parsing the version output.
Peter
CG
Christian Grün22 Feb 2025 11:44 #
Thanks, Peter, for the observation. We’ll see if we can fix this for an upcoming version [1].
Best,
Christian
[1] https://github.com/BaseXdb/basex/issues/2383
Quoted text · Peter Boot · 23 lines
On Mon, Feb 10, 2025 at 3:22 PM Peter Boot via BaseX-Talk < basex-talk at mailman.uni-konstanz.de> wrote: > Hello, > > I tried to install BaseX on Windows 11 and it kept giving me the message > that Java 11 was needed, even though I already was at 20 and now am at 21. > > Then I noticed that java --version also reported a JAVA_TOOLS_OPTIONS > environment variable: > > java --version > Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 > openjdk 21.0.6 2025-01-21 LTS > OpenJDK Runtime Environment Temurin-21.0.6+7 (build 21.0.6+7-LTS) > OpenJDK 64-Bit Server VM Temurin-21.0.6+7 (build 21.0.6+7-LTS, mixed mode, > sharing) > > After removing that variable it no longer appears in the output of the > version command and the install runs fine. I suppose it messes up > parsing the version output. > > Peter >
Written for BaseX 11.7. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery