UML profile default appearance not working for PackagingComponents

[ChrisIgel]

I'm currently creating an UML profile for our DDD process, which works as it should.
When extending metaclasses like Class or Component, I can either customize the the default appearance (F4) or add an _image property with shape scripts for my stereotypes.
After generating the MDG file and reloading the MDG technologies in EA, the stereotypes can be dragged on a diagram and have the expected appearance.
But if I try doing the exact same for the metaclass PackagingComponent, it doesn't work as expected. Only the border width is being considered and every other setting (including the shape scripts) are being ignored. The packaging components are always displayed with the default red background color. The weird thing is that I can customize my custom stereotypes after I dragged them on a diagram (both the default appearance and shape scripts via adding and assigning a stereotype).
Also I took a look in the UML profile XMLs and the bgcolor and other properties are set.

My configured UML profile with a shape script on the stereotype ACL and two default appearances on BoundedContext and SharedKernel looks like that:


The resulting elements look like that:


Am I doing something wrong or is this just not possible/a bug?

I am using version 12.0 but version 13.5 has the same issues.

[Geert Bellekens]

I suspect a bug, especially since PackagingComponents are relatively new members of the meta model.

Geert

[qwerty]

"Relatively" means "a couple of years", but I guess the number of people having used it so far is "relatively" small ;-) So smells like a bug.

q.

[ChrisIgel]

I guess I'll file a bug report then.
Any ideas on how to deal with this issue in the meantime? Maybe a regular component can somehow be linked to a package?

Thanks for the confirmation so far.

[Geert Bellekens]

Any specific reason why the meta-element you are extending has to be a PackagingComponent?

I would guess that using either a package or a component would be good enough.

Geert

[ChrisIgel]

Well packages would suffice in theory but if I'm not mistaken you can't put associations between packages.
On the other hand if I'm using components (which resembles BoundedContexts way better IMHO), the model belonging to (or into) the component would be decoupled, which is not what I want.

[qwerty]

You can't put associations between packaging components either.

q.

[ChrisIgel]

Well I just tried it with associations again and it works I guess