[
https://issues.apache.org/jira/browse/GIRAPH-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422094#comment-13422094
]
Alessandro Presta commented on GIRAPH-180:
------------------------------------------
Slightly related: in the long term, it would be ideal to make the "giraph"
script more robust and easy to use (I remember having to hardcode paths inside
it in order to make it work) so that users can run their own classes without
having to care about the Giraph jar, much like it is for Hadoop.
> 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
