[gemoc-dev] Discussion about possible folder refactoring

[Didier Vojtisek <didier.vojtisek@xxxxxxxx>]

Hi

I would like to propose a folder re-organisation in GEMOC repositories

In early releases of GEMOC, the only target was eclipse bundles 
(plugins, feature, update site, product). In this situation maven for 
the build + tycho for dependency mangement is fine and convenient
However,  we are trying to open the studio (at least the modeling 
workbench) to be more technology agnostic and propose other build. For 
example, pure maven jar in order to build java standalone components 
(ie. depenency management is done by maven and not the manifest files), 
or propose component that are actually built with non java languages  
(typescript, javascript, pyhton, ...) all these use their own build 
system (even tycho and pomfirst cannot be run in a single mvn command 
:-(  not speaking about compiling typescript ...)
A given GEMOC feature will then be availabable in several 
technologies/packaging

As I don't know any high level build system that is able to integrate 
other buid system (except a shell that call each build systems, or 
entirely rewrite the build in the new build system) It would be 
important to structure our folders in order to clearly identify the 
artefacts.

- My propositions:

keep the root folder corresponding to the high level features structure 
(ex: modeldebugging/framework/execution_framework, 
modedebugging/framework/xdsml_framework, modedebugging/commons, 
execution-moccml/ccsljava_xdsml, ...)
then instead of having directly "plugins", "releng" at that level (ie. 
the artefacts built by tycho to produce eclipse bundles), move down to a 
folder named "tycho"

this would leave a place to put "pomfirst" for pure maven artefacts, and 
"webapp" for typescript/javascript based artefacts

This would make clear what is available in each technology (and each 
build system)

My only concern is about git traceability, in my experience there is a 
small risk that moving folder will break the traceabily of the changes 
in the files. :-(

I'l try to minimize this risk by creating dedicated commit (no squash 
and merge for this one)  but I prefer to have your agreement first and 
also  your suggestion about the possible folder names (tycho, pomfirst, 
webapp)

Would you agree  with this move ? (a +1 is fine ;-) )

All the best
Didier


--
Didier Vojtisek
SED Rennes - DiverSE Team - LogicA Team
Inria, Univ Rennes, CNRS, IRISA
Campus de beaulieu
35042 Rennes
02 99 84 75 07