Hi Ede,
This week, several co-workers have had problems with their java
installation after an automatic update on their windows machine
(problems probably related to the enterprise update policy, not the
standard windows update).
On these machines, JRE is still present somewhere in Program Files (but
java was no more accessible from the path : java -version returns 'java
not found')
As a temporary solution, I decided to wrap a JRE in an OpenJUMP
distribution (reinstalling java was not an option). I used the
possibility to set a relative path to a JRE in the .bat file.
What I noticed and suprised me :
- on some machines where java was broken, the embeded version with an
appropriate JAVA_HOME was working from the .bat, *but not from the .exe*
- on some machines where java was broken, the standard version (without
customized JAVA_HOME), the .bat stopped working, *but the .exe still
worked* !
I did not check how the .exe works but I naively thought that it was
just a thin wrapper around the .bat. Have you some hints about how the
.exe works, and why it can behave this way ?
Michaël
------------------------------------------------------------------------------
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
