You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2015/09/09 03:33:45 UTC

[jira] [Updated] (BIGTOP-1494) Introduce Groovy DSL to replace bigtop.mk in Gradle build

     [ https://issues.apache.org/jira/browse/BIGTOP-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Boudnik updated BIGTOP-1494:
---------------------------------------
    Attachment: BIGTOP-1494.patch

Initial patch. All functionality works as before using new configuration format represented by {{bigtop.bom}} file. I still need to populate it with all the components in the stack. Perhaps need to add some checks for the sanity of the incoming bom file.

Current version is transitory and is made to avoid any major changes in the underlying components builds. That's why I am flattening the configuration structure to a map and using all these nasty FULLY_CAPITALIZED_WITH_UNDERBARS names for the varialbles.  

Would appreciate any early feedback. Thanks!

> Introduce Groovy DSL to replace bigtop.mk in Gradle build 
> ----------------------------------------------------------
>
>                 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
>            Assignee: Konstantin Boudnik
>             Fix For: 1.1.0
>
>         Attachments: BIGTOP-1494.patch
>
>
>  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)