Benjamin Heitmann commented on GIRAPH-180:


That would make it easier for new users, and for general managment of builds 
via maven. 

In addition, the Maven repository which will be used for publishing Giraph 
can also be used for publishing Maven archetypes (basically project specific 
skeletton code
without any functionallity). 

I was planning on making an initial version of a Maven archetype for a small 
Giraph job sometime in the next weeks. 
> 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: 
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to