Re: [papyrus-rt-dev] [Features] What should be the basic feature content

[Ernesto Posse <eposse@xxxxxxxxxxxxx>]

I think the discussion in Bug 502133 covers it.

So there are different meanings of "product", and Céline, correct me if I'm wrong, but I think you are asking about the "product" in the sense of what we package and deploy, as specified in the papyrusrt.product file, is that right?

My understanding from the discussions with Charles and Simon and in the bug, is that codegen and rts should be there for 0.8  (although not xtext), even if they are not considered the "base" set of features in some sense. I think this makes sense, because otherwise there would be a mismatch between what is installed by the Oomph setup and this packaged product. Furthermore, if a user downloads this product she would have to explicitly add the codegen update site to get the same set of features. 

PS: I'm responding here rather than in the bug because we are having connectivity issues with the Eclipse servers from our office.

--

Ernesto Posse

Zeligsoft

On Mon, Sep 26, 2016 at 6:17 AM Peter Cigéhn <peter.cigehn@xxxxxxxxx> wrote:

Hi,

I think that the current included features in the the basic Papyrus-RT feature is what should be there. So that looks good to me.

The picture that I drew way back, https://dev.eclipse.org/mhonarc/lists/papyrus-rt-dev/msg00215.html, I still feel is highly relevant. 

What is missing in that picture is the optional migration, compare and Xtext features.

What I would like too see is the code-gen and run-time features to be included in some top level C++ feature. If that is the current C++ core feature, or a new C++ feature, which then includes the current C++ core feature and the code-gen and run-time features I cannot say. But this should be anyway be separated from the basic Papyrus-RT feature (as indicated in the picture).

/Peter Cigéhn

On 26 September 2016 at 10:26, Céline JANSSENS <celine.janssens@xxxxxxxxxxx> wrote:

Hello Everyone,

 

Could you please let me know how the different features should be organized. I mean, what the basic Papyrus RT feature should include ?

 

Here is what is into the papyrus rt feature for the time being:

 

·         Oeprt.umlrt.common.feature

·         Oeprt.umlrt.common.ui.feature

·         Oeprt.umlrt.core.feature

·         Oeprt.umlrt.tooling.feature

·         Oeprt.umlrt.profile.feature

 

 

Are not include by default:

 

·         Oeprt.umlrt.cpp.feature

·         Oeprt.umlrt.migration.rsa.feature

·         Oeprt.umlrt.tooling.compare.feature

·         Oeprt. codegen-feature

·         Oeprt.rts-feature

·         Oeprt.xtumlrt.xtext.feature

 

 

Keep in mind that all the features are still available in the p2 to be installed separately.

The basic feature should contain the core part of Papyrus RT, and should work on his own !

 

This organisation is nothing related with the product that can contain several features, basic one and others…

 

Which features  need to be included into the basic papyrus-rt feature and is not ?

 

Best regards

Céline

 

 

 

_______________________________________________
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