[
https://issues.apache.org/jira/browse/BIGTOP-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jay vyas updated BIGTOP-1494:
-----------------------------
Description:
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.
was:
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 (i.e. declared 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.
> 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)
