[
https://issues.apache.org/jira/browse/MAHOUT-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891808#action_12891808
]
Peter Goldstein commented on MAHOUT-427:
----------------------------------------
I've been following along in parallel and have been able to get past the
ClassNotFoundExceptions. I'm synced up to r967257 but I have a couple of
classes in my src that are modified to include a setJarByClass call that are
not in the tree:
core/src/main/java/org/apache/mahout/ga/watchmaker/MahoutEvaluator.java
examples/src/main/java/org/apache/mahout/classifier/bayes/WikipediaDatasetCreatorDriver.java
examples/src/main/java/org/apache/mahout/ga/watchmaker/cd/hadoop/CDMahoutEvaluator.java
examples/src/main/java/org/apache/mahout/ga/watchmaker/cd/tool/CDInfosTool.java
Not sure if the setJarByClass is required in these classes, but they seem to
fit the pattern.
Now I'm getting an NPE in ClusterDumper, which is presumably what you are
running into.
> $MAHOUT_HOME/examples/bin/build-reuters.sh doesn't run successfully because
> of classpath issues related to the -core argument
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: MAHOUT-427
> URL: https://issues.apache.org/jira/browse/MAHOUT-427
> Project: Mahout
> Issue Type: Bug
> Affects Versions: 0.4
> Environment: Hadoop installation on EC2 as described here -
> https://cwiki.apache.org/MAHOUT/mahoutec2.html
> Reporter: Peter Goldstein
>
> Once I resolved issue MAHOUT-426 , I was still not able to run the
> ./examples/bin/build-reuters.sh script without errors These were
> ClassNotFoundExceptions, indicating a problem with the classpath.
> The issue appears to be related to the "-core" argument, which controls the
> classpath. Placing '-core' as the first argument to the individual
> $MAHOUT_HOME/bin/mahout calls in the script solved the issue, but I'm not
> sure it was the correct solution. It's unclear to me what the '-core'
> argument is supposed to signify.
> Can someone shed some light on this, and tell me whether this is the correct
> solution to the problem? And if not, what is the correct solution to this
> classpath issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.