Hello team.
I have a question about architecture, and probably Remi might be the right person to answer. But input from others is welcome too.
We have several transformations in the codegen and xtumlrt components, but not all transformations are necessarily code generation. For example, we have a transformation from textual UML-RT to a Papyrus-UML model, and I'm working on one from a Papyrus-UML model to textual UML-RT.
Some of these transformations, such as one that transforms from UML to xtUML-RT, are currently located in the codegen component.
Since these transformations are not necessarily code generation I'd like to move them out of there, so that they could be a separate feature, since we know that there are potential users interested in the modelling part (including textual) but not interested in code generation.
In order to move them out of codegen, and place them either under xtumlrt or under a new component, I need to move a couple of utility classes down the dependency chain, so that I don't get circular dependencies.
In particular these are some classes from our oeprt.codegen.utils package, such as UMLRealTimeProfileUtil, UMLRealTimeStateMachProfileUtil, and GeneralUtil (and possibly others).
I think that the "core" component looks like a good location for these.
So I have two questions:
1) Is it OK with the tooling team (and everyone) if I move these classes to core and common? (perhaps adding a new plugin)
2) Some of these classes are in Xtend. Would there be any objections to use Xtend in the core and common components?
Thanks,
--
Ernesto Posse
Zeligsoft
