From: pcm <pcm...@us...> - 2005-05-12 06:25:39
|
Update of /cvsroot/javapathfinder/javapathfinder In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv9219 Modified Files: default.properties Log Message: * added Config support for an alternate lookup dir, which should be used when JPF doesn't find a property file in the current dir, and before it tries to load the properties from resources. The dir is initialized from the +jpf.basedir=<dir> option, which is in turn now automatically set when using the bin/jpf script. This should make it easier to run JPF from within Eclipse, but outside its root dir (e.g. from where the application code resides) * hot fixed the BFSearch MJIEnv problem (ThreadInfo(ThreadData) ctor). THIS IS NOT YET THE REAL SOLUTION, since we want to get away from static references, but it buys us time to do the proper refactoring. Index: default.properties =================================================================== RCS file: /cvsroot/javapathfinder/javapathfinder/default.properties,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- default.properties 7 May 2005 00:40:01 -0000 1.2 +++ default.properties 12 May 2005 06:25:31 -0000 1.3 @@ -98,7 +98,7 @@ vm.classpath = build/examples # where do we look for sources (defaults assume we start in the JPF root dir) -# vm.sourcepath = src:examples:test +vm.sourcepath = ${jpf.basedir}/src:${jpf.basedir}/examples:${jpf.basedir}/test # where to get atomicity and other code execution attributes from vm.attributor.class = gov.nasa.jpf.jvm.DefaultAttributor |