Hello everyone,
We are setting up a topology of Capella libraries in order to collaborate through several partners, so that
- each can contribute material related to his focus,
- each can use some elements (interfaces, types) provided by others (with no possibility to create dependency cycles)
- each can have his own “internal” types
- each can deliver updates of his own library independently of others.
- one aggregating model assembles all PCs provided by the various libraries (through rec/rpl + deployment)
This creates a nice topology of libraries. and relies on a set of separate git repos and works fine.
Question 1:
Given one model and a set of libraries it depends on (libraries can form an acyclic graph),
is there some operator in Capella, that helps aggregate the model + all its libraries in one single model ?
(kind of a merge of model + all libraries)
(similar to what a linker when you link libraries within your exec)
Question 2 :
If it is not available, are there some difficulties to realize that? (is there something one should care about?)
Question 3 :
Since each library will evolve by itself, major states of each librar will act as “versions” .
=> Is there some advised way to annotate a library with a version number ?
(more serious/integrated than “readme.txt” or a custom “PropertyValue”)
kind regards
Franco