[
https://issues.apache.org/jira/browse/BIGTOP-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916172#comment-13916172
]
Konstantin Boudnik commented on BIGTOP-1227:
--------------------------------------------
bq. 3) can do release (deploy maven, make tag in different branch including
hadoop, hbase, etc instead of downloading tar from apache)
The main premise of Bigtop was - and still is - to build software stacks from
official Apache software releases. By the very definition, an ASF project
release is a tarball of source code. So, I don't see how #3 here can be
considered a "...general requirement for bigtop"
bq. //currently, build command is hard-coded like:
Yes, they are hard coded, because each component of the stack has its own way
of getting built. It is fragile, I agree. So please offer a way of doing this
in a better way.
bq. RPM should come from binary tar instead of fresh build
I am not sure what it means and where the binary tar is coming from, but I
believe it has been covered by my very first bullet point above.
At any rate, if you feel like there's some conceptual issues that prevent you
from doing certain things - let's start a {{[DISCUSSION]}} thread on the dev@
list. Jira isn't the most convenient way of doing it.
> Deploy artifacts to maven repository
> ------------------------------------
>
> Key: BIGTOP-1227
> URL: https://issues.apache.org/jira/browse/BIGTOP-1227
> Project: Bigtop
> Issue Type: Improvement
> Components: Build
> Reporter: Shengjun Xin
>
> When we use bigtop to build a distro, we need deploy the artifacts to our
> maven repo. For example, we need to deploy the hadoop artifacts to maven repo
> to make sure hbase can depend on it
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
