Ah! This is actually a problem I stumbled over recently as well. As I am constantly recompiling 2.x either after src or dependency changes I also noticed that it is extremely easy to find oneself with >1 version of a jar in various lib directories.
Thank for the heads up Lewis On Fri, Sep 28, 2012 at 3:10 PM, Bai Shen <[email protected]> wrote: > Actually, it turned out to be an incorrect fix. I was getting the error > because I had two copies of the job file in my directory. So when I ran > the nutch script, it wasn't returning the correct value when checking for > *nutch*.job. Changing the brackets made the error go away, but I still > wasn't able to get nutch to run until I removed the extraneous job files. > > On Fri, Sep 28, 2012 at 10:03 AM, Lewis John Mcgibbney < > [email protected]> wrote: > >> Hi Bai, >> >> If you could use the script @NUTCH-1087 [0] and provide insight into >> your findings it would be very much appreciated. It is the intention >> to integrate this into 2.x one it has been tested enough. The glitch >> you highlight is exactly the type of stuff we need to find. >> >> Thanks >> >> Lewis >> >> [0] https://issues.apache.org/jira/browse/NUTCH-1087 >> >> On Fri, Sep 28, 2012 at 2:52 PM, Bai Shen <[email protected]> wrote: >> > When running the nutch script in deploy mode using Nutch 2, I get a >> Binary >> > Operator Expected error. According to the following website, the fix is >> to >> > use double brackets. I tried it and it worked for me. >> > >> > >> http://digitalvectorz.wordpress.com/2009/12/10/bashshell-programming-binary-operator-expected/ >> >> >> >> -- >> Lewis >> -- Lewis
