[
https://issues.apache.org/jira/browse/MAHOUT-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982577#action_12982577
]
Sean Owen commented on MAHOUT-584:
----------------------------------
Looks OK, or rather, I made a different version of the patch that checks for
null rather than catches an NPE
However I can't get the test to pass; in the test environment it seems like
these are not on the classpath. Can you run the test?
> MahoutDriver throws NPE if driver.classes.props is not on the classpath
> -----------------------------------------------------------------------
>
> Key: MAHOUT-584
> URL: https://issues.apache.org/jira/browse/MAHOUT-584
> Project: Mahout
> Issue Type: Bug
> Affects Versions: 0.4
> Reporter: Frank Scholten
> Priority: Minor
> Fix For: 0.5
>
> Attachments: MAHOUT-584.patch
>
> Original Estimate: 0.08h
> Remaining Estimate: 0.08h
>
> Running MahoutDriver from an IDE run configuration with a program name such
> as kmeans and help as arguments, will result in an NPE because it won't be
> able to find the driver.classes.props file.
> By changing the catch block so it catches Exception instead of IOException,
> MahoutDriver will use the driver.classes.default.props file so it can still
> be run with or without the driver.classes.props. This is useful if one wants
> to call the MahoutDriver from custom code outside mahout instead of using the
> mahout script. However, if one wishes to run MahoutDriver from outside
> mahout, the mahout-core, -math, -utils and example jars still need to be on
> the classpath or else ClassNotFoundExceptions will be thrown when it tries to
> add the classes for all the programs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
