[news.eclipse.modeling.mdt.uml2] PackageMerge in UML metamodels

[Timothy Marc <timothymarc@xxxxxxxxxx>]

Hey,

just to let me know, whether i've understood the principle of 
PackageMerge correctly. Let's have a look on UML::Class, which is in the 
end and Classifier - SturcturedClassifier, BehavioredClassifier - 
EncapsulatedClassifer.

These depth of inheritance results of the execution of all merge 
relationships, which are defined in the model. Is this correct?

Currently, i'm digging a bit deeper into all the models, which 
constructs the merged UML model. But i had a lot af questions concerning 
the dependencies of all those models.

1. For what purpose is the Ecore.uml, 10536.uml, 10537.uml, UML2_2_UML.ecore

2. What are the differences between Superstructure and UML.merged? It 
seems to me, that UML merged results by the execution of package merge 
relationsships defined in UML.uml. The UML.uml merges the packages of 
the compliance levels. And the compliance levels refers to either the 
Infrastructure.uml and the Superstructure.uml.

It seems to me, that the Superstructure.uml, was modeled without any 
merge definition, just for the construction of the compliance levels. Is 
this correct? If so, i would have expected, that the Superstructure.uml 
merges the constructs and primitive types packages of the infrastructure 
as it is shows in figure 7.1 of the current UML Spec 2.2. But the only 
import, i found in the Superstructure.uml addresses the primitive types 
of the Infrastructure.

So, i would really appreciate it, if somepne could explain all this 
relationships to me, in particular the rational for the additional 
Superstructure.uml...

Thanks a lot
Timothy