You might want to use https://issues.apache.org/jira/browse/MAHOUT-680 this is the patch where the CLASSPATH variable was introduced.
https://issues.apache.org/jira/secure/attachment/12478208/MAHOUT-680.patch On Wed, Jun 8, 2011 at 3:07 AM, Alex Ott <[email protected]> wrote: > Yes, the problem is in the CLASSPATH setting - *-job.jar should be > before "standard" jars. > > so the code in line 121 should look like: > > # add release dependencies to CLASSPATH > for f in $MAHOUT_HOME/mahout-*-job.jar $MAHOUT_HOME/mahout-*.jar ; do > CLASSPATH=${CLASSPATH}:$f; > done > > I'll try to make "correct" patch for this issue and will create Jira entry > > On Tue, Jun 7, 2011 at 7:11 PM, 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 > > > > > > -- > With best wishes, Alex Ott > http://alexott.net/ > Tiwtter: alexott_en (English), alexott (Russian) > Skype: alex.ott >
