Re: [papyrus-rt-dev] Bug from Papyrus

[Ernesto Posse <eposse@xxxxxxxxxxxxx>]

Great! I can confirm that indeed your steps reproduce it. Good to know it was not my environment being "funny" again.

A bit of a follow-up inline below.

On Thu, Nov 3, 2016 at 2:55 PM Christian Damus <give.a.damus@xxxxxxxxx> wrote:

Ah!  Good news.

I have reproduced the ViewerSearchService exception.  The reason I wasn’t seeing it earlier was that I was trying to reproduce it in models that had diagrams open.

You will get this exception whenever you open the Model Explorer context menu if and only if you haven’t had any diagram open since opening the model.  As soon as you open some diagram, even if you close it afterwards so that only the Welcome page shows in the editor, then this exception will not occur.

I have raised bug 506997 on Papyrus.

Christian

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. 

How do I do that? I don't see any options for the ServiceRegistry in either the Model Explorer or the Papyrus Preference pages.

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.

I misinterpreted your sentence. I thought you were telling me to try something to see if the exception still occurs. (The perils of parsing a natural language that is not your mother tongue ;))

Well, except that I already installed other stuff, so I have to either go through the list of features and make sure I select only the Papyrus-RT features, or start a new dev environment from scratch (again). In the past I tried it and things where still missing. Perhaps it's better now, but I just tried it, and did the following: 1) deselected all features (so that I wouldn't have the extras); 2) selected the oeprt feature; 3) clickes on "Select Required", and it only added the oeprt.common, .common.ui, .core, .cpp, .profile and .tooling features. It didn't add the .codegen, .rts, xtumlrt or compare features, or anything down the line, in particular it didn't add the Papyrus features or event the eclipse platform. Addint the oeprt.rcp feature resulted in no changes. What's more, even if I select all features, and I click on "Validate Plug-ins", it shows a bunch of validation errors, related mostly to oep.infra.gmfdiag.common and dependencies to something called 'org.apache.batik.*".

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.

Ok, I didn't have to add oe.equinox.ds. I only had to add

org.apache.batik.util

org.apache.batik.util.gui

org.apache.batik.css

but I had to add the 1.6 version. I also had the 1.7 version, but the requirements asked for [1.6.0,1.7.0).

Quite annoying that there is no feature with the Batik stuff. If Papyrus uses them, couldn't Papyrus create a feature (e.g. org.eclipse.papyrus.infra.gmfdiag.batik.feature) and include all those dependencies?

Also, is the equinox bundle for something extra that you have?

--

Ernesto Posse

Zeligsoft