| Re: [papyrus-rt-dev] Bug from Papyrus |
Hi, Ernesto, See some follow-up, in-line. cW On 3 November, 2016 at 12:13:28, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
The round-tripping between UML and Ecore that is implemented by the UML2 model importer and exporter is quite solid.
I suppose so. I don’t know much about Sirius.
I use UML because the codegen extensions in UML2 for the semantics of UML class models offer advantages that I enjoy. Obviously, importing your existing Ecore models into UML won’t take advantage of those because they aren’t in your models, yet, so I can’t say that it would be worthwhile to migrate your models. There are a few purely codegen-related things that don’t require changing the actual model (e.g., creation methods, operations classes for multiple inheritance). I suppose it might be useful depending on what kind of evolution you anticipate in these models.
I don’t understand. What are you trying to do now? I was just saying that some code seems to be requesting a service from the registry before the registry is started. I have no idea where in the code, but I doubt it’s in the preference pages.
Oh. That looks like you’re opening a context menu when this exception happens. It sounded like this was an exception that were seeing when Papyrus start up. Which menu on what thing in the UI? None of the navigation-oriented context menus or menu-bar menus that I can find in Papyrus cause this exception. Maybe it’s not a Papyrus menu?
Yes, I think the 'Select Required' only works with manifest dependencies. It won’t know about Papyrus features because we only have dependencies to Papyrus bundles. I guess it finds some Papyrus-RT features because we have features that contain and/or import other features. In my launch configs, I do have to add the Batik bundles as extras because there is no feature anywhere that includes them. Likewise org.eclipse.equinox.ds. The Batik dependencies are the cause of the org.eclipse.papyrus.infra.gmfdiag.* issues.
|