Order in xmm file affects layout when imported class is involved #2
Description
Reordering the T/P sides in the xmm file should have zero effect on the layout.
But in this case, it does. Since this bug has never appeared before, I am assuming it is due to the rare case where we involve an imported class.
In the example from the SM metamodel relationship subsystem below, if you re-order the T/P sides in the xmm file, the multiplicity and phrase names reverse in the layout. Workaround is to just to ensure that the ordering matches in xmm and mls files.
