giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Heitmann (JIRA)" <>
Subject [jira] [Commented] (GIRAPH-180) Publish SNAPSHOTs and released artifacts in the Maven repository
Date Fri, 27 Jul 2012 11:20:35 GMT


Benjamin Heitmann commented on GIRAPH-180:

Hello Jaeho, 

sorry, I did not manage to start working on the Maven archetype. 
Mainly because I had to move to a graph different library for my actual work/research. 

However, I am keeping an eye on the lists, 
and I plan to revisit Giraph as soon as the 0.2 release is finalized.
At the current speed of changes to Giraph, using it from trunk is not a good idea for beginners
anyway IMHO, so having the archetype before the 0.2 release wont help anybody probably. 

But I could have another look at the maven archetype then if nobody else wants to start it
before 0.2.
> Publish SNAPSHOTs and released artifacts in the Maven repository
> ----------------------------------------------------------------
>                 Key: GIRAPH-180
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message