The o.e.prt.rts plugin contains the model library and it is where we are deploying the C++ runtime.
As Charles says, the model library is language agnostic. I don't know who decided to bundle the two in the same plug-in, though.
I do agree with the idea of having a separation between the language-agnostic parts and the C++ codegen/rts.
Since the library is language agnostic, shouldn't it go in the main feature?
I'm not sure I understand why o.e.prt.core.cpp should depend on the model library, specially since the library is language agnostic.
Nevertheless, I'm OK with the modifications proposed.
Perhaps we could create a separate plugin for the C++ rts (say called o.e.prt.rts.cpp) and leave o.e.prt.rts with only the model library, or rename it to something like o.e.prt.modellib, and possibly include that in the main feature?
To do this split we need to make some adjustments to our POM files, and since we use the model library in the generator, any refactoring would have an impact and we need to make the necessary adjustments.
PS: I'm leaving on vacations tomorrow until April 4th, so I have limited time today to do any necessary adjustments on our end.