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.
Attachments
Attachments
Issue Links
- breaks
-
BIGTOP-2033 Build order of the stack is broken
- Resolved
- is blocked by
-
BIGTOP-1495 Remove make build system
- Resolved
- is related to
-
BIGTOP-1477 Gradle build should print errors
- Open
-
BIGTOP-1718 add facility for printing out BOM in json format
- Resolved