v15.2 - Allow traversal of nested packages in MDG profil generation from package

[Paolo F Cantoni]

After many days of (unsuccessfully) fighting MDG profile generation from a diagram^[1], I changed over to profile generation via package.  This works, but I now have to do some extra setup to make the profile have similar properties to that generated from a diagram (for example, I now have to add _sizeX and _sizeY attributes to get the sizing required).

One thing that we want to do is to retain the grouping of the stereotypes to be emitted by the use of multiple nested packages.  We can emit each separately, via automation, and then aggregate them in the mts file generation.  However, it causes issues of naming conflicts - which can be solved with a relatively simple edit.  It is, however, tiresome to have to do this every time.

It seems to us that if the traversal of the nested packages were allowed, one profile could be emitted - the ID being based on the GUID Of the topmost package (as at present).  We feel this would be a very useful additional functionality.

Thoughts?
Reported,
Paolo

^[1]  'Coz it's broken, BADLY!