giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-642) Add Maven release profile for Giraph
Date Mon, 04 Nov 2013 07:55:17 GMT

    [ https://issues.apache.org/jira/browse/GIRAPH-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812667#comment-13812667
] 

Roman Shaposhnik commented on GIRAPH-642:
-----------------------------------------

In addition to what was described above we also need to have a capability for publishing Maven
artifacts for Hadoop 1.x and Hadoop 2.x compiled Giraphs. The proposal here is that Hadoop
1.x remains to be the default
and Hadoop 2.x compatible Giraph gets released with a hadoop2 classifier.

> Add Maven release profile for Giraph 
> -------------------------------------
>
>                 Key: GIRAPH-642
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-642
>             Project: Giraph
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 1.0.0
>            Reporter: Lewis John McGibbney
>             Fix For: 1.1.0
>
>
> When reviewing the RC's recently I noticed that the RAT plugin (which is really useful
for ensuring license headers and various other bits and pieces are nicely addressed for releases)
target does not work.
> Over in Gora [0], we have a real nice target which runs the Maven rat, source,  javadoc,
gpg and checksum plugins in order hence creating the exact RC compliant artifacts we wish
to review before pushing the release.
> It should be trivial to implement something similar for Giraph and would also hopefully
simplify the release process somewhat for the RM as well! 
> [0] http://svn.apache.org/repos/asf/gora/trunk/pom.xml  



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message