for many companies, in all but few very small projects that use Melody (Capella) to do model-based system enigineering, Melody Advance Team is the de facto standard and the models are Team projects i.e. models located in remote repository, not local projects. This setting allows for shared coordinative work of multiple team menbers to take place in the same model, which is something that the Melody Advance does not support. Of course, in such projects documentation generation is also important. This raises the question why there is no availability of m2doc for Team projects? Is there any plan to add it?
I am aware of the differences between Melody Team and Melody and also about the background of all this but nevertheless the possible workarounds are not good. Would Obeo and/or TCE recommend any preferred way how to integrate m2doc template/gencof and a Team project? The ultimate goal is to automatize or integrate m2doc document generation into a kind of CI process, which also necessitates a CLI (as clarified here M2DOC command line interface)