| Re: [mdt-papyrus.dev] Compilation errors in extendedtypes and paletteconfiguration projects |
|
Hi Christian, I don’t see these plug-ins on master. IIRC, they have been renamed (and moved) to oep.infra.extendedtypes.* and oep.uml.tools.extendedtypes.* in 0.9.x The current plug-ins should be: oep.infra.extendedtypes.* oep.infra.extendedtypes.emf oep.uml.tools.extendedtypes They all properly compile (on both master and streams/0.10-maintenance) Regards, __________________________ Camille Letavernier +33 (0)1 69 08 00 59 -
camille.letavernier@xxxxxx CEA LIST - Laboratoire d'Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE) Papyrus :
http://www.eclipse.org/papyrus De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Christian W. Damus
I pulled the latest from Git (commit 2979cde) this morning (EST) and have compilation errors in several projects related to the "extendedtypes" model:
These plug-ins all are still trying to use APIs from the 0.7 version of the extendedtypes model, which has just been significantly refactored in the 1.0 version. Should I have these plug-ins in my workspace (are they obsolete)? I suppose
it may be useful to continue maintaining them at least for debugging purposes ... Moreover, the last of the plug-ins in this list is actually included in nightly builds. Is it going to be removed from the build? Also, I have compilation errors in the oep.paletteconfiguration.editor project (it uses the wrong package names in references to classes in the oep.uml.diagram.paletteconfiguration.edit plug-in; it just needs to be re-generated). This
plug-in is not in the nightly builds. Is it obsolete? Thanks, Christian |