This runs a script with execution debugging: sh -x script.sh It is very useful when you want to debug a problem like this once, and then later on do not want to see the same debug printout over and over
On Tue, Jun 7, 2011 at 10:11 AM, Sean Owen <[email protected]> wrote: > Indeed, the script sets CLASSPATH, and that's likely where the problem is. > It could be (is almost likely to be) a bug. We should probably just have the > script print these things out -- if you want to throw in a quick "echo" like > Dhruv says and show the result, that might point directly at the problem. > > On Tue, Jun 7, 2011 at 5:43 PM, Alex Ott <[email protected]> wrote: > >> There was no CLASSPATH set (I already had intersection with Lucene 2.x >> that was used for one of my projects, and I removed this env variable) >> - this is why I'm asking > -- Lance Norskog [email protected]
