Hi, Ernesto,
See some replies in-line, below.
HTH,
Christian
On 2 November, 2016 at 16:00:57, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote: I'm not on Oxygen. I recreated the dev environment to make sure I was on Neon.1. I have installed in my dev environment a few extras such as:
a) CDT b) CMake Editor c) Dynamic Languages Toolkit - ShellEd IDE d) Ecore Diagram Editor (SDK)
There has been a history of incompatibility between the ECore Diagram Editor and GMF-based applications, in particular Papyrus. IIRC, older releases up to something like 2.0 were okay to combine with Papyrus but the latest releases, not so much. But I don't know the details. Issues have been raised numerous times in the EMF and/or Papyrus forum; googling may find you some useful details. Myself, I always do my class modeling in UML, with Papyrus for diagrams. It’s like Ecore++: compatible with ECore, with several very useful extras.
I don't think any of these should be relevant. b) and c), strictly speaking, are not necessary, but it's a pain not to have them. But I couldn't do without a) and d).
My launch configuration is set to use "all workspace and enabled target plug-ins".
Yeah, I never do that. Only the features that are actually supposed to be in Papyrus(-RT). And certainly not the tests.
I do have some unrelated projects in my workspace, but I close them before launching. I do however keep the Papyrus-RT test bundles open. These shouldn't cause any trouble, should they? I would expect that the dev environment should work as smoothly as possible with whatever we have in the repo.
I don’t know about the Papyrus-RT tests, in particular, but there are Papyrus test bundles that add all sorts of weird extensions that make for a bizarre user experience in the tool.
In any case, the error is a very Papyrus-specific error. "Registry should be started before" ??? What sort of thing can cause Papyrus to raise that?
Attempt to get a service out of the ServicesRegistry of the model editor (or other usage of a ModelSet) before the registry has been started. But what component is doing that? Perhaps you can provide more of the stack.
I may change my launch configuration as you suggest, but that has the drawback that if something new is added, you have to remember to manually update the launch configuration, and in the past I fell for that. It's very easy to forget to update this.
That’s why assembling the launch config from features is so handy. Unless there’s a whole new feature to add, you can’t just forget a bundle here or there. And because, unlike Papyrus, Papyrus-RT doesn’t define features for the tests, you can probably just let the launch config find all features in your workspace and target, which gives you the best of both worlds.
Nope, I’ve never seen that.
On the latest Papyrus-RT master with the latest Papyrus Neon.2 nightly, I get only the usual “Xyz is already registred [sic] elementtype [sic] but it is not binded [sic] yet” errors. Are you perhaps mixing Papyrus master (Oxygen) content with Papyrus-RT? Or do you have test bundles in your run-time launch configuration?
Now that we have a Papyrus-RT RCP, I simulate an RCP launch by launching the Papyrus-RT product with all of the (non-test) Papyrus and Papyrus-RT features selected, not using plug-ins to define the launch configuration. Maybe that could help you to eliminate some bad interaction?
Christian
Whenever I launch a runtime instance from the development environment I am getting a lot of exceptions from Papyrus like this one:
!MESSAGE Unexpected Error !STACK 0 org.eclipse.papyrus.infra.core.services.BadStateException: Registry should be started before. (Service= 'org.eclipse.papyrus.infra.services.viewersearch.impl.ViewerSearchService', state= registered) at org.eclipse.papyrus.infra.core.services.ServicesRegistry.getService(ServicesRegistry.java:406) at org.eclipse.papyrus.infra.core.utils.AbstractServiceUtils.getService(AbstractServiceUtils.java:117)
Has anyone else experienced this?
-- Ernesto Posse Zeligsoft
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|
