[
https://issues.apache.org/jira/browse/BIGTOP-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133474#comment-14133474
]
Roman Shaposhnik commented on BIGTOP-1373:
------------------------------------------
Sorry for coming to the party rather late, but here's what I'm confused about:
# we already agree that Makefile-based builds are getting removed in 0.9.0.
No point in massaging that functionality.
# in our current Gradle-based infrastructure everything is keyed-off of the
URL and hence is trivial to add custom logic to handle different types of
protocols (even imaginary ones).
Based on the two points above, shouldn't the point of this JIRA be about making
sure that whatever URL you put in bigtop.mk as a *_SITE/*_ARCHIVE that the
protocol gets handled correctly? Today we only handle http:// and file:// but
there shouldn't be any reason not to add things like git:// as first class
citizens.
Am I missing something?
> 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.3.4#6332)
