You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Mark Grover (JIRA)" <ji...@apache.org> on 2014/08/10 19:35:12 UTC

[jira] [Commented] (BIGTOP-1373) Add a mechanism of obtaining source for components from SCM

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

Mark Grover commented on BIGTOP-1373:
-------------------------------------

Seems like we are all leaning towards the bigtop-github.mk patch. Julien, is there anything else that needs to be changed there or is this good to go?
I noticed that it only had the github values for HBase, all other components had rather dummy values copied from bigtop.mk. It would be good to update them to be github based as well. Apart from that, it's looking good to me.

Thanks again for working on this!

> Add a mechanism of obtaining source for components from SCM
> -----------------------------------------------------------
>
>                 Key: BIGTOP-1373
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1373
>             Project: Bigtop
>          Issue Type: Improvement
>            Reporter: Julien Eid
>         Attachments: BIGTOP-1373-extrafile.patch, BIGTOP-1373-noextrafile.patch, BIGTOP-1373.patch
>
>
> This was brought up here (https://issues.apache.org/jira/browse/BIGTOP-1363) as a much wanted feature for our build system so we can build against branches. I have two approaches to doing this that I'll be posting up Patch files for and seeing which approach everyone likes better. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)