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

Roman Shaposhnik commented on GIRAPH-794:
-----------------------------------------

Please disregard the hudson failure. This appears to be related to a whole 
bunch of Giraph tests running simultaneously on the same node. I'll re-run the 
job shortly. In the meantime, the other job with the same change finished ok: 
https://builds.apache.org/view/E-G/view/Giraph/job/Giraph-trunk-default-deploy/5/

> add support for generic hadoop1 and hadoop2 profiles
> ----------------------------------------------------
>
>                 Key: GIRAPH-794
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-794
>             Project: Giraph
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 1.0.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 1.1.0
>
>         Attachments: 
> 0001-GIRAPH-794-add-support-for-generic-hadoop1-and-hadoo.patch, 
> 0001-GIRAPH-794.-add-support-for-generic-hadoop1-and-hado.patch
>
>
> I would like to propose that as part of Giraph 1.1.0 we introduce generic 
> hadoop1 and hadoop2 profiles that would be expected to track latest releases 
> on hadoop 1.x and hadoop 2.x codelines (currently these are 1.2.1 and 2.2.0). 
> These profiles will be the ones used to publish Giraph maven artifacts. 
> Following the convention established by HBase I propose that we bake hadoop1 
> and hadoop2 tokens into a version.
> Thus every release of Giraph starting from 1.1.0 will deploy the following 
> versions:
>    * <version> (same as <version>-hadoop1)
>    * <version>-hadoop1
>    * <version>-hadoop2
> Thoughts?



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to