[
https://issues.apache.org/jira/browse/GIRAPH-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812690#comment-13812690
]
Lewis John McGibbney commented on GIRAPH-642:
---------------------------------------------
Roman, recently (yesterday) I was talking with Renato (one of Giraph's GSoC
students this year). I was trying to build Giraph locally and hit a problem
where Giraph core and core-test artifacts are not available in
repository.apache.org.
Is there any particular reason for this? I am aware that most builds on Jenkins
are not stable so maybe pushing unstable snapshots is not a great idea, however
I was just surprised that the build relies upon snapshot's (for tests) which
are not available anywhere!
wdyt?
> 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)
