Re: [papyrus-rt-dev] Papyrus Designer dependencies in Oomph setups

[Céline JANSSENS <celine.janssens@xxxxxxxxxxx>]

Hi Peter,

 

In RCP this is what I did. I reference dependencies of the following plugins on the rcp feature (as I don’t know exactly which feature requires those plugins)

 

·         org.eclipse.papyrus.designer.languages.common.base

·         org.eclipse.papyrus.designer.languages.cpp.library

 

And when building RCP, the “oep.designer.languages.common.profile” dependency is added implicitly

 

Regards

Céline

 

 

 

De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part de Peter Cigéhn
Envoyé : mardi 18 octobre 2016 16:44
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : Re: [papyrus-rt-dev] Papyrus Designer dependencies in Oomph setups

 

Hi,

 

Yet one more aspect to iron out of the 0.8 release I guess... :)

 

I need to double check though since you mention one plugin that I cannot see referenced in the tester setup (and thus also the end-user setup that Christian currently is updating for the 0.8 release).

 

The oep.designer.languages.common.profile I cannot see referenced from the tester setup. And I would not expect us to really have a dependency to it either. To my knowledge we do not use any of the profiles from Designer since we decided to go the custom RtCppProperties profile that it specific to the code-generator in Papyrus-RT.

 

So what I then would expect is to only have 

 

org.eclipse.papyrus.designer.languages.common.base

org.eclipse.papyrus.designer.languages.cpp.library

 

in the Oomph setup files.

 

But as we have discussed here https://bugs.eclipse.org/bugs/show_bug.cgi?id=505416#c63 we should probably add the dependencies to some existing feature (or add a new feature). You a free to follow up on my comment in https://bugs.eclipse.org/bugs/show_bug.cgi?id=505416#c67.

 

If we do that, then we do not have to keep track of these implicitly in the Oomph setup files, and we can easier align the Oomph setups and the RCP.

 

/Peter Cigéhn

 

On 18 October 2016 at 16:02, Ernesto Posse <eposse@xxxxxxxxxxxxx> wrote:

Hi everyone.

 

We noticed that the "Open CDT Editor" option still appears in the context menu in both the tester and developer Oomph setups. This is because the setups still have a dependency on oep.designer.languages.cpp.cdt.texteditor.

 

We also have a dependency on 

 

- oep.designer.languages.common.extensionpoints

- oep.designer.languages.common.base

- oep.designer.languages.common.profile

- oep.designer.languages.cpp.library

 

but we only need the last three, as we are no longer using the extension points.

 

Are there any objections to remove the unused designer dependencies from the setup models?

 

I'm still familiarizing myself with the new build infrastructure, so I don't know if any changes here might yield something inconsistent with the POMs.

 

--

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