[
https://issues.apache.org/jira/browse/GIRAPH-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198050#comment-13198050
]
Jakob Homan commented on GIRAPH-136:
------------------------------------
Yeah, I had seen that as well. It's a bit of a different issue. This happens
when one tries to run bin/giraph from the dev environment (without a lib
directory). We can add in the giraph jar from /target to the classpath and add
the complete classpath for dependencies (via maven dependencies:classpath or
whatever the syntax is), but this will still fail if the jar isn't present.
This would be a bit messy, but would be in line with other Hadoop ecoystems
bin/scripts...
The current JIRA is addressing user experience from the package.
> Erorr message for bin/giraph could be improved
> ----------------------------------------------
>
> Key: GIRAPH-136
> URL: https://issues.apache.org/jira/browse/GIRAPH-136
> Project: Giraph
> Issue Type: Improvement
> Affects Versions: 0.1.0
> Reporter: Jakob Homan
> Assignee: Jakob Homan
> Fix For: 0.2.0
>
> Attachments: GIRAPH-136.patch
>
>
> Currently when one just runs bin/giraph without the required jar, the message
> isn't very helpful:
> {noformat}[tardis giraph-0.1]$ bin/giraph
> Can't find user jar to execute.{noformat}
> It would be better to have a more in-depth message explaining Giraph and what
> is expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
