B4J Question Problem configuring path to Java library

[Adrian Jansen]

Hi,
Using Windows 11
Just updated my old version of B4J to the latest version 10.30
Downloaded the latest Java library JDK 19.0.2 and unpacked it using 7-zip to c:\Java\jdk-19.0.2 folder
Opened the IDE and used Tools|Configure paths to point to c:\Java\jdk-19.0.2\bin\javac.exe
When I close that dialog and try to compile a program, I get a heap of errors in the compile dialog:
B4J Version: 10.30
Parsing code. (0.00s)
Java Version: 8
Building folders structure. (0.00s)
Compiling code. (0.01s)
Compiling layouts code. (0.01s)
Organizing libraries. (0.00s)
Compiling generated Java code. Error
System.Exception: Cannot find: C:\Java\jdk-11.0.1\jdk-11.0.1\bin\javac.exe
Please configure paths (Tools - Configure Paths).
at fe.a(Process A_0, Boolean A_1, DataReceivedEventHandler A_2,

Looked again in the Configure paths, and indeed it still points to the older path to jdk-11.0.1, the old version I used to use., which I deleted.
Seems to be stuck on that path, and wont accept the new one, even when all I do is change the path to the new one, close the Configure paths dialog and reopen it.

Any ideas would be appreciated

 

[LucaMs]

Any ideas would be appreciated

Mine is just an "idea," Erel will be more helpful.

If I understand correctly, you open the dialog, set the new path, close the dialog, reopen it immediately and the old path "is back".

This makes me think you're not being granted permission to modify the b4xV5.ini file, that you don't have the rights.
Perhaps the best thing to do is reinstall B4J, making sure to do so with administrator rights.

 

[Adrian Jansen]

Thanks for that. I had installed with admin rights. That was not the issue, It seems I had two older installs, one in Program Files, and the other in Program Files (x86) . Somehow these both must have been using the same ini file, and that never got correctly updated. Deleted the one in Program Files (x86), then reinstalled the new one again with admin rights in Program Files and it all seems to work ok. Thanks for putting me on the right track.

Now to fix the next bug.....