Hi, Team,
In order not to block the fixing of bugs in capsule structure inheritance (e.g.,
511380) and to get past the hurdle of the modelled façade refactoring, I would like to merge
Gerrit 89958 as soon as possible. After, of course, review by some suitable volunteer (don't worry — at least half of it comprises icon files, generated model interfaces, the generated UML extensions that don't have custom code, plus loads of tests 😉).
The problem is that this commit cannot pass the Gerrit builds as currently structured and I don't see any way to tease it apart into a sequence of commits that can each be individually reviewed and merged before the next. The reason is that, although from an API perspective for most clients the modelled façade is a drop-in replacement for the API currently on master, because now the façade objects are EObjects, they are recognized differently by UI frameworks such as the Papyrus Properties View. Trying to commit the façade API first would break the UI tests, but the UI cannot be changed in advance because the façade objects would not yet be EObjects. Moreover, because the modelled façade is a drop-in replacement for the existing API, I cannot first add the new façade in its entirety, then switch the UI over to using it, and finally delete the old façade because the API names are all identical: they cannot both be built and deployed together (that is the whole point of the drop-in replacement).
The only way I see out of this is just to push the change directly to master once the reviewer(s) is/are satisfied with it. All of our JUnit tests for affected components pass when run locally and the tooling seems still to work. Unless somebody can suggest a solution that I'm not seeing?
Comments welcome, as are reviewers, of course.
