Indirectly adding configurations of the same component to the same Global Configuration

Updated Request:

Use Case Reuse of Components in Large Systems:

We create Global Configurations representing reusable Software components (e.g., Diagnostics).

These Software components are reused in different versions and variants in different products (also represented by Global Configurations), e.g., a Brake System or a Motor.

Finally, we assemble these products to large systems, e.g., a Vehicle, represented by another Global Configuration.

This way of working is essential to us but cannot be implemented because we will get a component skew in the overall Vehicle Global Configuration.

Our request: We must be able to assemble Vehicles without getting components skew. We want the possibility, to create baselines in this Vehicle Global Configuration, to save a specific state of this Configuration. It is not necessary, that not-unique links can be resolved if a user is working in this Vehicle Global Configuration.

Original Request:

We want to create complex systems and products based on smaller parts.
This we think can best be done by creating hierarchy of GCs that reflects the product architecture.
At the same time we reuse Software libraries in different variants in different products and product parts.
These Software Variants are managed as substreams in the same Components.
The usage of Software Variants in the different product parts that in turn are part of an overall system finally leads to an undesirable component skew.

Definition: Indirectly adding configurations of the same component to the same Global Configuration A is done by adding a GC B and a GC C to GC A where both B and C contain a local configuration from the same component.
Requirements:
- We would like to be able to indirectly add local configurations of the same local component to the same Global Configuration without getting a warning of a component skew.
- If we indirectly add configurations of the same component to the same Global Configuration, we want to get a neutral indication that this is the case.
- If we directly add configurations of the same component to the same Global Configuration, we still want to get a warning of a component skew.
- In case we want to view a link to an artifact that is indirectly contained inside of the GC A in more than 1 variant, the user shall be asked to choose GC B or C as configuration contexts to view the link in.
- In case we want to create or modify a link to an artifact that is indirectly contained inside of the GC A in more than 1 variant, the user shall be asked to choose GC B or C as configuration contexts to create the link in.
- in case we create a report on GC A on an artifact with a link to an artifact that is indirectly contained inside of the GC A in more than 1 variant, JRS shall report all variants of the linked artifact.