Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [papyrus-rt-dev] No diagram created for Capsule and SM
And then there’s the work being done on viewpoint switching that, I would hope, will help us in handling composition of the various Papyrus variants (including Papyrus-RT) and automatically switch the viewpoint, for example, when the perspective changes.

But that’s the future… :)


Regards,

Charles Rivet
Senior Product Manager, Papyrus-RT product lead

On 2016.11.07, at 03:20 , Peter Cigéhn <peter.cigehn@xxxxxxxxx> wrote:

Hi,

This issue is tracked by https://bugs.eclipse.org/bugs/show_bug.cgi?id=478298. The current work around is the we set the preference for the UML-RT viewpoint either in the Oomph setup file (using a preference task) in the end-user/tester setup, and for the RCP build the preferences are set using the plugin_customization.ini mechanism. For any installation that is not based on any of these, e.g. the run-time workbench in the development environment, the preference for the view point must be set manually until https://bugs.eclipse.org/bugs/show_bug.cgi?id=478298 have been resolved.

We now have at least one more occasion of the "recurring problem" mentioned in this Bugzilla... :)

/Peter Cigéhn

On 4 November 2016 at 19:03, Ernesto Posse <eposse@xxxxxxxxxxxxx> wrote:
Hi. The viewpoint is not activated in the development environment, but it is in the deployed product, so end-users won't have that problem.


On Fri, Nov 4, 2016 at 12:29 PM SMAOUI Asma <Asma.SMAOUI@xxxxxx> wrote:

Thanks Ernesto, it was a problem with the viewpoint activation, the UML RT was not selected in the papyrus preference page.

 

Asma

 

De : Ernesto Posse [mailto:eposse@xxxxxxxxxxxxx]
Envoyé : vendredi 4 novembre 2016 17:16
À : SMAOUI Asma <Asma.SMAOUI@xxxxxx>; papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>


Objet : Re: [papyrus-rt-dev] No diagram created for Capsule and SM

 

One more thing that you might want to try before starting from scratch is to pull the website repo (papyrus-rt) and then Perform Setup Tasks. The website repo has updated setup models which include updated dependencies and repositories. As a general rule, I always pull from at least the website repo before performing setup tasks.

 

Other than that, maybe you have an additional feature that conflicts with Papyrus?

 

--

Ernesto Posse

Zeligsoft

 

 

On Fri, Nov 4, 2016 at 12:07 PM SMAOUI Asma <Asma.SMAOUI@xxxxxx> wrote:

Hello,

Thanks Ernesto for your help, I tried Help à Perform Setup Tasks and I use now the last version of Papyrus (nightly)

But I still get the same pb (no diagram is created)

 

I debug a little bit and I found that the pb comes from this code in the method that creates the capsule diagram : protected Diagram createCompositeDiagram() in the CapsuleEditHelperAdvice:

In fact, the method CreateHeadlessCapsuleStructureDiagramCommand().createDiagram(..) is never called cause most of the PapyrusView have no name (name = null) so view.geName() is never equals to CapsuleUtils.UML_RT_CAPSULE_DIAGRAM.

 

 

for (ViewPrototype prototype : prototypes) {

       PapyrusView view = prototype.getConfiguration();

       if (view != null && CapsuleUtils.UML_RT_CAPSULE_DIAGRAM.equals(view.getName())) {

return new CreateHeadlessCapsuleStructureDiagramCommand().createDiagram(modelSet, capsule, capsule, prototype, null, false);}

}

 

I will try to set the environment from scratch.

 

P.S I can also reproduce the Service issue that you talked about in your previous mail, and that Christian succed in reproducing it as well J

 

Asma

De : Ernesto Posse [mailto:eposse@xxxxxxxxxxxxx]
Envoyé : vendredi 4 novembre 2016 15:55
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>; SMAOUI Asma <Asma.SMAOUI@xxxxxx>
Objet : Re: [papyrus-rt-dev] No diagram created for Capsule and SM

 

I just tried it and I have no problems: creating a capsule or state machine creates the corresponding diagrams.

 

Asma, I would suggest doing a "Help->Perform Setup Tasks..." in your dev environment to make sure you have the right bundles in your TP.

 

--

Ernesto Posse

Zeligsoft

 

 

On Fri, Nov 4, 2016 at 9:08 AM Christian Damus <give.a.damus@xxxxxxxxx> wrote:

Hi, Asma,

 

That is strange.  Do you see any exceptions in the workspace log?  Are you up-to-date with the latest on the Papyrus Neon maintenance branch?

 

Master is the only active branch of Papyrus-RT and it should not behave in this way.

 

Christian

 

 

On 4 November, 2016 at 09:01:39, SMAOUI Asma (asma.smaoui@xxxxxx) wrote:

Hello,

 

I fetch the last master branch version from upstream. when I create a capsule, no capsule diagram is created, same thing with State Machine. I checked the notation file, no diagram were there.

Should I checkout another branch (not master) ?

 

Thanks

 

Asma

_______________________________________________
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


_______________________________________________
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

Back to the top