[ 
https://issues.apache.org/jira/browse/GIRAPH-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rob Vesse updated GIRAPH-180:
-----------------------------

    Attachment: GIRAPH-180.patch

Attaching a patch which contains a minor modification to the Giraph parent POM 
necessary towards resolving this issue.

This simply modifies the POM to point to the Apache parent POM as its parent 
which means the POM picks up the appropriate configuration for deployment 
targets.

In principal with this in place a Giraph committer can then run {{mvn deploy}} 
at the command line to deploy the SNAPSHOTs.

I tried this myself since I am an Apache committer but I get a Forbidden error 
from the Nexus server (repository.apache.org) so I assume that is configured to 
only allow project committers to push SNAPSHOTs for their projects (I know my 
credentials are valid because I've pushed SNAPSHOTs for the project I 
contribute to in the past).

Likely the next step once this patch is accepted will be to look at setting up 
appropriate Jenkins jobs on the Apache build server that will deploy the 
SNAPSHOTs on a regular basis.  Once this patch is committed I can start looking 
into doing that.

> 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, 1.0.0
>            Reporter: Paolo Castagna
>            Priority: Minor
>         Attachments: GIRAPH-180.patch
>
>   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 was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to