| Re: [mdt-papyrus.dev] Architecture Framework: issue in sysml 1.1 |
|
Hi Mickaël, Restoring org.eclipse.papyrus.infra.types.core.elementTypeSetConfiguration extensionpoints in plugins\sysml\org.eclipse.papyrus.sysml.service.types\plugin.xml seems to fix all problem in SysML 1.1 BDD. In the same idea, removing these extension points broke my SysML 1.4 prototype. You can probably temporary restore it, to move forward on palette. Regards, Benoît De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de MAGGI Benoit Hi Mickael, I just tested SysML 1.1 Oxygen and indeed Block isn’t working but Requirement works fine. I don’t know why the Requirement diagram behave correctly and not BDD. I made a prototype for SysML 1.4 [1] It works correctly but for the moment
I kept the old extension point for elementtype (basically it was to keep the unit tests passing) I will try to remove these extension points and keep you updated. Regards, Benoît 1:
https://git.eclipse.org/c/papyrus/org.eclipse.papyrus-sysml.git/log/?h=committers/bmaggi/oxygen De :
mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Mickael ADAM Hi, I have an issue which seems to be due to the new Architecture framework. In a sysml 1.1 diagram, in the model explorer when I try to create a new SysML child (for example Block), it only creates the the metaclass (Class) without the application
of the stereotype. It appears that a workaround is to put the sysml.block element type into the
org.eclipse.papyrus.infra.services.edit.TypeContext Context. So it seems that new architecture.SysML context is not taken into account. This bug appears also in my work with palette configuration model, when I bind tool directly to sysml element type instead of UML element + stereotype application. A4T team has the same issue. Anybody have an idea to resolve it?
Thanks. Mickaël |