[
https://issues.apache.org/jira/browse/BIGTOP-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361471#comment-14361471
]
Konstantin Boudnik commented on BIGTOP-1725:
--------------------------------------------
The second sentence is really about this: you're suggesting to remove the nulls
directly in the list of the components. Which potentially has wide effect all
across the package creation layer. What I am proposing is to only call this
{{denull}} functionality right where it really affects the output - namely in
the JSON formatting routine. Basically right here {{packages.gradle:105}} - you
can just add one more transformation to the {{collect}} call. Does it make
sense?
> Exclude null values from BOM json output added in BIGTOP-1718
> -------------------------------------------------------------
>
> Key: BIGTOP-1725
> URL: https://issues.apache.org/jira/browse/BIGTOP-1725
> Project: Bigtop
> Issue Type: Improvement
> Components: general
> Affects Versions: 0.8.0
> Reporter: Jonathan Kelly
> Assignee: Jonathan Kelly
> Priority: Minor
> Fix For: 0.9.0
>
> Attachments: 0001-exclude-null-values-from-BOM-json-output.patch,
> BIGTOP-1725.patch
>
>
> BIGTOP-1718 added support for a new bom-json task that outputs the BOM in
> json format, but the original format would include all possible fields with
> nulls for missing fields. This patch removes all fields with null values in
> order to make the output cleaner.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
