You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2014/10/24 04:37:34 UTC

[jira] [Commented] (BIGTOP-1494) Cleanup packages.gradle to just read from a gradle data structure

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

jay vyas commented on BIGTOP-1494:
----------------------------------

similar to BIGTOP-1477, possibly can be merged as a minor cleanup task for the {{packages.gradle}} file.

> Cleanup packages.gradle to just read from a gradle data structure 
> ------------------------------------------------------------------
>
>                 Key: BIGTOP-1494
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1494
>             Project: Bigtop
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.8.0
>            Reporter: jay vyas
>            Priority: Minor
>             Fix For: 0.9.0
>
>
>  Seems confusing to have a {{.mk}} file which is mostly just a bunch of variable declarations, which is then parsed as a CSV, simply for the sake of guiding the {{packages.gradle}} file .  
> Can we be more idiomatic to gradle and either eliminate {{bigtop.mk}} by making it into a native gradle data structure (its really just an array,  and we can  declare in gradle.settings) , so that the {{readBOM}} function is easier to follow ?
> I think it is an entry point to understanding bigtop's build system so we should try to simplify it as much as possible to make it maximally easy for people to understand how bigtop's gradle packaging system works.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)