You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@giraph.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2013/04/17 01:47:15 UTC

[jira] [Updated] (GIRAPH-642) Add Maven release profile for Giraph

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

Lewis John McGibbney updated GIRAPH-642:
----------------------------------------

    Issue Type: Improvement  (was: Bug)
    
> 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.0.1
>
>
> 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 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