| Re: [mdt-papyrus.dev] Impact of EMF facet 0.2 |
|
Yes it is correct, these plugins must be removed. They have been remove from the build De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Christian W. Damus Looking at the history of the org.eclipse.papyrus.sdk feature.xml, it looks like the new org.eclipse.papyrus.emf.facet.feature replaces the org.eclipse.papyrus.infra.queries.feature. In that case, all of these are obsolete:
Is this correct? If so, there are still dependencies in the test suite and feature on these obsolete test bits. Thanks! Christian On Mar 13, 2014, at 2:48 PM, Christian W. Damus <give.a.damus@xxxxxxxxx> wrote:
Thanks for the heads-up, Patrick! This looks great. One question: the org.eclipse.papyrus.core.queries.test project now has a bunch of compilation errors because the entirety of the QueryUtil API has been commented out. Is this test project obsolete? Thanks, Christian On Mar 13, 2014, at 11:33 AM, TESSIER Patrick 202707 <Patrick.TESSIER@xxxxxx> wrote:
Hi, The usage of EMF-Facet 0.2 has been integrated into Papyrus. This usage involves one major change. In the context of old framewok, to obtain the UML element from the model explorer, it was only needed to adapt it into an EObject. Now this approach does not run. In fact all elements in the model explorer that are directly displayed with EMF- Facet are EObjects. See org.eclipse.papyrus.emf.facet.custom.metamodel.v0_2_0.internal.treeproxy It implies that the test with IAdaptable does not un. Now , I advise you to use import org.eclipse.papyrus.infra.emf.utils.EMFHelper; … obj = EMFHelper.getEObject(obj); … Patrick Laboratoire d'Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE) CEA Saclay Nano-INNOV - Institut CARNOT CEA LIST, DILS - Point Courrier n° 174 - 91 191 Gif sur Yvette CEDEX _______________________________________________ |