Hi Jukka,
It seems that the new oj_windows.bat works in a similar way than
openjump.bat did before. However, openjump.exe is obviously behaving
in a different way. It does not any longer just launch the batch file
and therefore edits made to oj_windows.bat do not have any effect if
OJ is started vie openjump.exe. Is OpenJUMP.ini there for configuring
what happens if OJ is started from the exe file, and if yes, how
should that .ini file be edited? For example to show the path to Java
version or to set proxy?
Yes, openjump.exe + openjump.ini are about the same as oj_windows.bat
Now that ede has normalized script names to oj_osname.ext, maybe I
should rename openjump.exe and openjump.ini to oj_windows.exe and
oj_windows.ini. But I think I have to give .exe and .ini the same name
(which does not fit with the idea to have a platform independant
.ini...). What do you think ede ?
Michaël
-Jukka Rahkonen-
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
