| Re: [mdt-papyrus.dev] [PROVENANCE INTERNET] Re: Extraplugins: Remaining dependencies to EMFFacet |
|
Hi, Ø
What about migrating these dependencies to the new release of EMF-Facet 1.0.0 ?
We’ve patched a lot of things in Papyrus/Facet to make it work, and to improves performances, and add new features. I haven’t had the opportunity to look into EMF Facet 1.0 to see if it would make
sense to migrate. Plus, we use our own metamodel URIs, so any custom/facet model would be broken. Since the M4 build is tomorrow, migrating to Papyrus Facet is the only viable solution for now (The alternative being to disable – partially – these plug-ins if they can’t be fixed for tomorrow) Camille De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de MAGGI Benoit Hi, Indeed there are some failings in extra dependencies. These plugins still reference org.eclipse.emf.facet.* org.eclipse.papyrus.infra.table.modelexplorer org.eclipse.papyrus.robotml.modelexplorer org.eclipse.papyrus.team.collaborative.controlmode org.eclipse.papyrus.texteditor.modelexplorer What about migrating these dependencies to the new release of EMF-Facet 1.0.0 ?
Regards, Benoit Maggi De :
mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de LETAVERNIER Camille Hi all, In Mars, EMF Facet will release its 1.0.0 version. The EMF Facet 0.1.x metamodel will be removed in M4 (i.e., it has already been removed). Some of the Papyrus Extra components still rely on EMF Facet, and won’t compile
anymore. Please have a look at the build result and remove all dependencies to EMF Facet 0.1.x plug-ins (This includes *.uiCustom and *.facetSet models): https://hudson.eclipse.org/papyrus/job/Papyrus-Master-Extra/ All *.uiCustom models should be replaced with *.custom (From papyrus.emf.facet.* plug-ins), and *.facetSet with *.facet (From papyrus.emf.facet.* as well). The queries contained in *.querySets models should now be defined
as Facet Operations Thanks, |