Skip to Main Content

collect relative path problem with java experiments

nevgenievMar 24 2014 — edited Mar 25 2014


There is an error in way collect writes or analyze/er_print reads java experiments

for java experiments run with relative paths like

collect ... -j path_to_java path_to_java/bin/java -cp ../../relative/path/some.jar

experiment is being written w/o resolving relative paths. So if later I run anzlyzer or er_print from any other directory other than original, stack traces won't contain line numbers. search/map paths do not work for it (or I didn't find a way to specify it in correct way)!

jar ignorance (needless to say they're not archived either) makes java experiments very fragile and hard to work with...

am I missing something or it's just the way it's supposed to work?

Post Details
Added on Mar 24 2014
1 comment