I am moving this into the next sprint pending simplification of the IGB build system.
Reason is:
There are a large number of changes to files, reflecting flaws in our architecture.
I feel that this many changes – and the massive amount of effort Noor had to expend just to understand what is going on – simply to support foreground color settings coming from the parsed file itself – ought not to have been necessary. I would like dig a little deeper to understand the ways our architecture made this necessary. It should be easier!
To use an analogy from the building trades: You should not have to install an entirely new wall simply to hang a painting.
However, our build system is overly complex, with a massive level of technical debt left over from older, more primitive versions of mvn. I think this needs to be improved (simplified and clarified) before attempting any major restructuring or analysis of the data intake (parsing) systems.
Noor Zahara - please keep your branch "live" on your fork, with the commits as they are. I am going to reject the pull request, but please be aware that this is not a reflection on your work. This is just so that the pull request no longer appears in the pull request queue while we deal with the blocking issue.
Un-assigning to give another devloper a chance to pick this up since NZ & ST discovered a good fix for
IGBF-1552& NZ will be working on that next.