[
https://issues.apache.org/jira/browse/GIRAPH-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Homan updated GIRAPH-136:
-------------------------------
Attachment: GIRAPH-136-b.patch
Here's a version that tries to be a bit smarter. If there's no lib directory,
it checks for a target directory (if target doesn't exist, it exits) and loads
the giraph jar from there and sets the classpath via maven (as described above).
This will work for dev enviroments with a hadoop instance. Invariably, this
won't work for someone and need to be modified more, but that's how these
scripts end up becoming so convoluted.
> 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-b.patch, 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
