I created TUSCANY-3374 to report the fact that we currently lose useful context from a problem determination perspective in the first phase of building. If I understand correctly the flattening that goes on in this phase happens before any issues with the contribution are detected. Coupling this with the fact that top level composites are automatically included behind the scenes into the domain composite (which is an implementation detail, and not a concept that the user is aware of), and the domain composite has no name, we find that all error messages are reported without a composite name.
Does anyone have any particular ideas on how best to solve this issue? I think we used to build included composites before the flattening process, in which case the context is still available, but at the time there was an issue in wiring between components in a given contribution, and the flattening helped address this issue. I think we may be in a better position now to address this. Would it be best to hang extra context on the artefacts as we flatten, or should we think about changing the way this build process happens? Ideas welcome. Kelvin.
