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

Konstantin Boudnik commented on BIGTOP-1494:
--------------------------------------------

As discussed in  BIGTOP-1718 a time for DSL has come. On the same ticket, Rob 
has implemented the JSON format to represent the stack and component. To 
refresh it looks like this:

{code}
{
    "version": "0.9.0",
    "components": [
...
        {
            "name": {
                "project": "zookeeper",
                "pkg": "zookeeper",
                "relNotes": "Apache Zookeeper"
            },
            "tarball": {
                "destination": "zookeeper-3.4.5.tar.gz",
                "source": "zookeeper-3.4.5.tar.gz"
            },
            "url": {
                "site": "http://apache.osuosl.org/zookeeper/zookeeper-3.4.5";,
                "archive": 
"http://archive.apache.org/dist/zookeeper/zookeeper-3.4.5";
            },
            "version": {
                "base": "3.4.5",
                "pkg": "3.4.5",
                "release": "1"
            },
            "git": {
                "repo": null,
                "ref": null,
                "dir": null
            }
        }
    ]
}
{code}
I'd say something similar expressed in Groovy should work as a DSL. Thoughts?

> 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: 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)

Reply via email to