Hyunsik Choi commented on GIRAPH-64:

The patch looks nice!
I have really wanted this feature!

However, when I applied the patch to trunk and executed 'mvn 
assembly:assembly', it caused some error as follows:

[INFO] Compiling 14 source files to 
[INFO] --- maven-surefire-plugin:2.6:test (default-test) @ giraph ---
[INFO] Tests are skipped.
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ giraph ---
[INFO] Building jar: 
[INFO] --- maven-assembly-plugin:2.2:single (make-assembly) @ giraph ---
[INFO] Reading assembly descriptor: 
[WARNING] NOTE: Currently, inclusion of module dependencies may produce 
unpredictable results if a version conflict occurs.
[INFO] Building tar : 
[WARNING] Entry: 
 longer than 100 characters.
[WARNING] Resulting tar file can only be processed successfully by GNU 
compatible tar commands
[WARNING] Entry: 
 longer than 100 characters.
[INFO] <<< maven-assembly-plugin:2.2:assembly (default-cli) @ giraph <<<
[INFO] --- maven-assembly-plugin:2.2:assembly (default-cli) @ giraph ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11.818s
[INFO] Finished at: Fri Nov 04 00:36:35 KST 2011
[INFO] Final Memory: 21M/413M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-assembly-plugin:2.2:assembly (default-cli) on 
project giraph: Error reading assemblies: No assembly descriptors found. -> 
[Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 

I'm using mvn 3.0.3 and sun-jdk 1.6.0_26.
I have surveyed this problem. I still don't know whether this is some bug or my 

Any one knows what is problem?
> Create VertexRunner to make it easier to run users' computations
> ----------------------------------------------------------------
>                 Key: GIRAPH-64
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-64
>             Project: Giraph
>          Issue Type: New Feature
>            Reporter: Jakob Homan
>            Assignee: Jakob Homan
>         Attachments: GIRAPH-64.patch
> Currently, if a user wants to implement a Giraph algorithm by extending 
> {{Vertex}} they must also write all the boilerplate around the {{Tool}} 
> interface and bundle it with the Giraph jar (or get Giraph on the classpath 
> and playing nice with the implementation).  For example, what is included in 
> the PageRankBenchmark and what Kohei has done: 
> https://github.com/smly/java-Giraph-LabelPropagation  It would be better if 
> we had perhaps a Vertex implementation to be subclassed that already had all 
> the standard Tooling included such that all one had to run would be (assuming 
> the Giraph jar was already on the classpath):
> {noformat}hadoop jar my-awesome-vertex.jar my.awesome.vertex -i jazz_input -o 
> jazz_output -if org.apache.giraph.lib.in.text.adjacency-list.LongDoubleDouble 
> -of org.apache.giraph.lib.out.text.adjacency-list.LongDoubleDouble{noformat} 
> This wouldn't work with every algorithm, but would be useful in a large 
> number of cases.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to