You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2015/02/21 00:30:12 UTC
[jira] [Comment Edited] (BIGTOP-1697) Bootstrap: hook up toolchain
into gradle build
[ https://issues.apache.org/jira/browse/BIGTOP-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329752#comment-14329752 ]
Konstantin Boudnik edited comment on BIGTOP-1697 at 2/20/15 11:29 PM:
----------------------------------------------------------------------
Here we go. There might be a better way to do it, but at least this will bridge the gap for now.
was (Author: cos):
Here we go
> 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)