[
https://issues.apache.org/jira/browse/BIGTOP-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329757#comment-14329757
]
jay vyas edited comment on BIGTOP-1697 at 2/20/15 11:32 PM:
------------------------------------------------------------
Excellent idea. Im almost on the verge of saying , since the toolchain is
really just for building, and we can do that in dockerfiles, someday "apply
toolchain" can be replaced w/ "docker pull".
But thats another conversation.
+1 ! on the patch
was (Author: jayunit100):
Excellent idea. Im almost on the verge of saying , since the toolchain is
really just for building, and we can do that in dockerfiles, someday "apply
toolchain" can be replaced w/ "docker pull".
But thats another conversation.
+1 !
> Bootstrap: hook up toolchain into gradle build
> ----------------------------------------------
>
> Key: BIGTOP-1697
> URL: https://issues.apache.org/jira/browse/BIGTOP-1697
> Project: Bigtop
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.8.0
> Reporter: Konstantin Boudnik
> Assignee: Konstantin Boudnik
> Priority: Critical
> Fix For: 0.9.0
>
> Attachments:
> 0001-BIGTOP-1697.-Bootstrap-hook-up-toolchain-into-gradle.patch
>
>
> We can simplify the bootstrap of the development environment by hooking the
> toolchain right into the gradle build.
> Thanks to the development of {{gradlew}} now you don't need to have anything
> on a system to have a functional build. I'd say a need to run {{puppet
> apply}} manually is going against this great paradigm: users needs to go
> through README files and try to figure out what to do. I'd rather do
> {{gradle toolchain}} that will run {{sudo puppet apply...}} under the hood
> and deliver a functional environment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
