[
https://issues.apache.org/jira/browse/BIGTOP-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348134#comment-14348134
]
Konstantin Boudnik commented on BIGTOP-1494:
--------------------------------------------
Addressing the point about name.* thing - definitely a miss on my account
{code}
bigtop {
stack: [version: "0.9.0, jdk: "1.7.0", scala: "2.10.3", groovy: "2.4.0"]
components [
component [name: "bigtop-groovy", project: "bigtop-groovy",
pgk; "bigtop-groovy", relNotes; "Grovvy: a dynamic language
for the Java platform"] {
tarball destination: "bigtop-groovy-2.3.8.tar.gz", source:
"groovy-binary-2.3.8.zip"
url site: "http://dl.bintray.com/groovy/maven/";, archive:
"http://dl.bintray.com/groovy/maven/";
version base: "2.3.8", pkg: "2.3.8", release: "1"
// Optional, as only null values are specified
git repo: null, ref: null, dir: null
}
component {
...
}
...
]
}
{code}
the groovy versions in question are for SDK and the runtime to be delivered
with the stack. So, in this case it isn't at odds. But potentially it might be
the case and that would make to enforce at the object creation level when the
DSL is getting consumed? Any other ideas around it?
> 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)
