We (me and my team) recently started using Capella and we are facing a few issues.
I have 2 models, a model M1 and a model M2. Model M2 is an addendum to Model M1.
The PCs on which M1 and M2 reside cannot communicate with each other due to restrictions so sharing a model via repository or even using the Team 4 Plugin is not an option.
Capella manages the model in a single xmi file.
I will work on both M1 and M2 causing diversions.
The issue is not with the versioning system, but in the merging of M1 in M2 (i.e. the two xmi files)
- Regularly, M1 will need to be merged into M2, causing merging issues, which are not easily solved with the current merging tool:
o If not cherry picking both versions, either all M2 additions are deleted during merge, or all M1 deletions will not be merged
o There is no easy way to verify if the merge is successful in the sense that the M1 base of the M2 model is equal to the M2 model
o Cherry-picking the xmi itself is difficult because the structure of the file is complex, with many ids and references
How do I split the model over different projects and/or files and still be able to reference the entities between these files or projects?
If this is not the proper channel to ask this question could you please direct me to the correct channel?