Hi all, is there any way to upload the template and genconf file in a Capella project that is uploaded in a Team-For-Capella repository?. In another thread (M2doc in Melody Advance Team (Capella Team)), I have seen the following answer from @YvanLussaud @MSechny , but it is from 3 years ago, in case the issue has evolved or there is another way.
The answer: “You can put the template in the CDO repository (shared project) and reference is with its URI (cdo://…). It will work as long as you have the SiriusSession defined to your shared .aird.
But in order to share the genconf file and be able to launch it, you will need to write a bit of integration code since M2Doc relies on resources from the workspace for its menus. Here you probably want to provide menus for each genconf resource on the CDO repository.
An other way of sharing a template is creating a plug-in and distribute it in an update site. There is a registry to reference template from such plug-ins.”
1 Like
Hi David,
Team for Capella manages only files/models which are part of the “session”: .capella, .afm, .aird and images. It is currently not intended to manages others files/resources.
Genconf and m2doc templates are not managed by Team for Capella.
Those files will not be shared nor retrieved by Team for Capella Export/Import wizard nor by the CLI tools nor by the connected project once connected.
The approach proposed by Yvan was a possible technical lead requiring some UI to manage the files sent those files to blobs on the repository but then additional integration would be required to manage evolution or collaboration on those files and avoid conflicts.
Currently I would say that an approach would be to have a companion project to your Capella project, with the .genconf, the .docx templates and the result target. Then you might manage version of this projects and its templates in your SCM tool like Git and have in it two .genconf files, one for the local generation, one for the generation from the connected project.
A few versions ago, documentation of M2Doc was slightly modified to mention how to adapt an existing genconf entry point from a local project to a connected project:
- Reference Documentation - M2Doc
- Open you connected project and authenticate
- Update the value of the SiriusSession path in Options (expert) tab to match the path of your connected project and .aird.
- Use the Edit button on the Variables tab to update/retrieve the self variable values.
Do not hesitate to contact us on your Team for Capella support channel.
Regards
1 Like
Okay, thanks for the info Maxime!
Have a nice day!