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

["Konstantin Boudnik (JIRA)" <ji...@apache.org>]

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

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

Ok, after looking into this a bit more, here's a bit more polished variance
{code}
bigtop {
  version = "1.1.0"
  stack {
    jdk    = "1.7.0"
    scala  = "2.10.3"
  }
  components {
    component {
      name    = "bigtop-groovy"
      project = name
      version {
        base = "2.4.4"
        pkg = base
        release = "1"
      }
      pgk = "bigtop-groovy"
      relNotes = "Groovy: a dynamic language for the Java platform"
      tarball {
        destination = "bigtop-groovy-${version.base}.tar.gz"
        source = "apache-groovy-binary-${version.base}.zip"
      }
      url {
        site = "http://dl.bintray.com/groovy/maven/"
        archive = site
      }
      // Optional, as only null values are specified
      git {
        repo = null
        ref = null
        dir = null
      }
    }
    component {
      name    = "bigtop-utils"
      project = name
      version {
        base = bigtop.version
        pkg = base
        release = "1"
      }
      pgk = "bigtop-utils"
      relNotes = "Service package for Apache Bigtop runtime"
      tarball {
        destination = "bigtop-utils-${version.base}.tar.gz"
      }
    }
  }
}
{code}

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