[
https://issues.apache.org/jira/browse/GIRAPH-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421864#comment-13421864
]
Jaeho Shin commented on GIRAPH-180:
-----------------------------------
[~metaman] Have you made some progress on a Maven archetype for Giraph?
I also believe providing an archetype with published artifacts will lower the
entry barrier significantly for new users. Many new users, including myself,
go through the same difficulties running even the simplest example code, partly
because they are also new to Hadoop in general. Even worse, when they try to
write their own vertex outside giraph source tree, it becomes a very
complicated task requiring clear understanding of Maven, Hadoop and Java
CLASSPATH all together for them. (See [today's thread on -user
list|http://mail-archives.apache.org/mod_mbox/giraph-user/201207.mbox/%3cCAH=L3WMwsn1DeRY9S6+zYMK2-=8avdxzn6fzbadqoo7p5iq...@mail.gmail.com%3e]
for example).
So, I think the archetype should include the fat-jar assembly recipes to embed
giraph into the jar, as well as a link to the wiki or short README on how to
launch it. It seems Maven central is for released versions, and if Giraph 0.2
release isn't happening soon, publishing SNAPSHOT jars to the Apache snapshot
repo and making the archetype depend on them might be a good start.
I went through the process of using Giraph as a noob not knowing much about
Hadoop or Maven, so I think I can write a helpful guide for beginners from
their perspective. If no archetype work has been done yet, I would be happy to
contribute some of my code as well, once the SNAPSHOT jars are published
somewhere. Or, for the moment, we could tell users to publish artifacts to
their local repo first, and generate a fresh project outside the Giraph source
tree and start playing from there. The archetype can be derived from an
existing project, so maybe the first step is to organize example vertex codes
into a subproject. I'll create a new issue for archetype if there isn't.
> Publish SNAPSHOTs and released artifacts in the Maven repository
> ----------------------------------------------------------------
>
> Key: GIRAPH-180
> URL: https://issues.apache.org/jira/browse/GIRAPH-180
> Project: Giraph
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.1.0
> Reporter: Paolo Castagna
> Priority: Minor
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Currently Giraph uses Maven to drive its build.
> However, no Maven artifacts nor SNAPSHOTs are published in the Apache Maven
> repository or Maven central.
> It would be useful to have Apache Giraph artifacts and SNAPSHOTs published
> and enable people to use Giraph without recompiling themselves.
> Right now users can checkout Giraph, mvn install it and use this for their
> dependency:
> <dependency>
> <groupId>org.apache.giraph</groupId>
> <artifactId>giraph</artifactId>
> <version>0.2-SNAPSHOT</version>
> </dependency>
> So, it's not that bad, but it can be better. :-)
--
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
