From: Peter C. M. <pcm...@em...> - 2005-10-06 22:29:01
|
> Before that, I tried the command line "+vm.bootclasspath = c:...", but > oddly enough it did not solve the problem. Just noticed that command line key/value Strings were not trimmed, causing this to add "vm.bootclasspath " instead of overloading "vm.bootclasspath". It's fixed, but as always it takes a day until that reaches the public CVS archive. I also forgot to quote shell arguments in the bin/jpf startup script, but I don't have a Windows version at hand to see if the same applies to jpf.bat > A very tiny issue is that the online docu says that the default > property > file is "default.properties". The help menu ("jpf" or "jpf -help") > says > the default is "jpf.properties". It seems the online docu is correct. both of them are loaded. The load order is default.properties (might be looked up via "+jpf.basedir=<jpf-dir>" command line arg) jpf.properties (or whatever file you specify with the "-c <mode- property>" command line arg) "+<key>=<value>" command line args i.e. command line args override everything. default.properties is used to specify all the internals JPF needs, but users rarely change. The mode property file "jpf.propeties" (or its replacement) shoudl contain application specific settings like listeners or report options. The command line is just to quickly play around with different settings. -- Peter |