Bug 354389

Description Yannick DIDIERJEAN 2011-08-10 11:00:17 EDT

Since the migration of Xpand/Xtend eclipse framework from 1.0.1 version to 1.1.0 some problems appears using org.eclipse.sphinx.xtend.typesystem.emf.ConfigurableEmfMetaModel.
Context of use:
The problem has been observed in an importer application using Xtend mecanisms.
The importer is a model to model transformer using Xtend.
The importer application is deployed in final application as a jar.
To contribute the correct metamodel descriptors for typesystem mecanism we use the class org.eclipse.sphinx.xtend.typesystem.emf.ConfigurableEmfMetaModel, in our example two MetamodelDescriptors are added one for Autosar 3x and one for Fibex 2.0.1 model.During the execution only one metamodel is fully operative, the second one seems to be partially recognized. After debugging this appear to be a problem linked to the packages retrieved by typsesystem (through metamodel descriptors) mecanisms while creating types.Unfortunatly we are so far unable to completly isolate the reason for that problem and the changes that occured in Xpand/Xtend leading to this issue.
This seems to be the same kind of problem as the one previously observed with
 "org.eclipse.sphinx.examples.hummingbird20.transform.xtend"  and so this probably means a need for adapting sphinx Xpand/Xtend metamodel contributor mecanisms to new version of Xpand/Xtend.