Re: [papyrus-rt-dev] Architecture issue on uml library of the runtime

[Peter Cigéhn <peter.cigehn@xxxxxxxxx>]

Hi,

I am not sure I understand the build aspect. You say that "the build of core or the core.cpp somehow include the build of the o.e.p.rts plugin". Well, I am not sure about this about core. I expect that it should be possible to install Papyrus-RT without the C++, run-time and code-gen features, and only have core, e.g. if you only are using Papyrus-RT for structure modeling (and are not interested in the behavior modeling with state machines, and any of the code-generation stuff).

Actually, I would like to remove the dependency from the top level Papyrus-RT Feature to the Papyrus RT Core C++ Feature which we currently have (and possibly renamed it into Papyrus RT Language C++ or something)

The top level Papyrus-RT Feature should only depend on the Papyrus RT Core, Papyrus RT Profile and Papyrus RT Tooling. 

The run-time and the code-generator are separate from the top level Papyrus-RT feature, and I guess the C++ language specific feature should be the same. The generic language framework should of course be included in core, but the extension on top of it (including the dependency to the run-time model library, which potentially could be language dependent).

Whenever we add additional languages in the future (Java, Alf, C) then you should be able to select only the language(s) you actually want to use. You shall not be "forced" to get C++ (as you do now if you select to install the top level Papyrus-RT feature).

Or do you foresee that we shall handle this differently regarding how to install the "optional" features of Papyrus-RT, for the use cases where only structure modeling is being used?

/Peter Cigéhn

On 17 March 2016 at 10:24, SCHNEKENBURGER Remi 211865 <Remi.SCHNEKENBURGER@xxxxxx> wrote:

Hi all,

 

I currently have a small issue [1] on the UML library for the current runtime (plugin o.e.prt.rts).

It would be required by the core.cpp feature, which declares initially the support for the C++ runtime. The library is required for example by the cpp core plugin, which indicates that this library should be loaded when the C++ language is used.

 

More on this feature is described here:

Bug 488104: Identify UML-RT system classes in UMLRT-RTS model library

https://bugs.eclipse.org/bugs/show_bug.cgi?id=488104

Bug 477721: Decide on common principle to identify system protocols,

including base protocol in UML-RT model library

https://bugs.eclipse.org/bugs/show_bug.cgi?id=477721

 

That indicates that the build of the core or the core.cpp should somehow include the build of the o.e.p.rts plugin. Do you have any objection towards this ?

 

Moreover this library is declared as a java plugin, where I do not see any code. Are there any plans to add code there?

Finally, I would recommend to split as done for the profile some changes in the dependencies and extension points:

-        I do not see the need for a gmf.runtime dependency there

-        I would not add the papyrus extension there, but rather in a tooling plugin. With that extension point removed, there are no dependency towards Papyrus UI, and so no need to have Papyrus installed to use the library (useful for example for basic command line model transformation)

Do you see any objection on that modifications?

 

Regards

Rémi

 

[1] https://git.eclipse.org/r/#/c/67560/

-------------------------------------------------------

 

Rémi SCHNEKENBURGER

+33 (0)1 69 08 48 48

CEA Saclay Nano-INNOV

Institut CARNOT CEA LIST

 

www.eclipse.org/papyrus

 

_______________________________________________
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