prepare independend module repos

[RolandJentschETAS]

📌 Description

Preparation for independend module repositories. Turn link direction and preparation for linking of interfaces.

See eclipse-score/score#2346

🚨 Impact Analysis

• This change does not violate any tool requirements and is covered by existing tool requirements
• This change does not violate any design decisions
• Otherwise I have created a ticket for new tool qualification

✅ Checklist

• Added/updated documentation for new or changed features
• Added/updated tests to cover the changes
• Followed project coding standards and guidelines

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run //src:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.3.0) and connecting to it...
INFO: Invocation ID: 2ac96e41-530a-44e3-bd7b-ac315d5e4ac1
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: src
Loading: 0 packages loaded
    currently loading: src
Analyzing: target //src:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //src:license-check (1 packages loaded, 0 targets configured)

Analyzing: target //src:license-check (58 packages loaded, 9 targets configured)

Analyzing: target //src:license-check (68 packages loaded, 9 targets configured)

Analyzing: target //src:license-check (75 packages loaded, 9 targets configured)

Analyzing: target //src:license-check (76 packages loaded, 9 targets configured)

Analyzing: target //src:license-check (128 packages loaded, 1178 targets configured)

Analyzing: target //src:license-check (132 packages loaded, 2516 targets configured)

Analyzing: target //src:license-check (140 packages loaded, 2576 targets configured)

Analyzing: target //src:license-check (140 packages loaded, 2576 targets configured)

Analyzing: target //src:license-check (140 packages loaded, 2576 targets configured)

Analyzing: target //src:license-check (140 packages loaded, 2576 targets configured)

Analyzing: target //src:license-check (144 packages loaded, 4589 targets configured)

INFO: Analyzed target //src:license-check (145 packages loaded, 4715 targets configured).
[12 / 16] JavaToolchainCompileClasses external/rules_java+/toolchains/platformclasspath_classes; 0s disk-cache, processwrapper-sandbox ... (2 actions running)
[14 / 16] JavaToolchainCompileBootClasspath external/rules_java+/toolchains/platformclasspath.jar; 0s disk-cache, processwrapper-sandbox
INFO: Found 1 target...
[16 / 16] no actions running
Target //src:license.check.license_check up-to-date:
  bazel-bin/src/license.check.license_check
  bazel-bin/src/license.check.license_check.jar
INFO: Elapsed time: 24.570s, Critical Path: 2.50s
INFO: 16 processes: 12 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 16 total actions
INFO: Running command line: bazel-bin/src/license.check.license_check src/formatted.txt <args omitted>
usage: org.eclipse.dash.licenses.cli.Main [-batch <int>] [-cd <url>]
       [-confidence <int>] [-ef <url>] [-excludeSources <sources>] [-help] [-lic
       <url>] [-project <shortname>] [-repo <url>] [-review] [-summary <file>]
       [-timeout <seconds>] [-token <token>]

[github-actions]

The created documentation from the pull request is available at: docu-html

[MaximilianSoerenPollak]

Can you explain this PR more? I have zero context what this should solve or why this is needed?

[RolandJentschETAS]

Can you explain this PR more? I have zero context what this should solve or why this is needed?

I have added a link and the required (coming) meta model picture into to the description of the PR. This was discussed and agreed in the Process Community and prevent cyclic links between repositories. It as well supports independent development in the feature module repos.

The current solution have problems with cyclic linking between repos and therefore is not or only difficult usable. The now visible linkage have only links in one direction from one repo to another.

So we have to change the link direction and have to add a link to the interfaces.

[MaximilianSoerenPollak]

First time I see that picture to be honest, but I will have a look later and see if I can understand.

[RolandJentschETAS]

First time I see that picture to be honest, but I will have a look later and see if I can understand.

It is the meta model picture from S-CORE process (which is the the base for the requirements to the docs-as-code) : See https://eclipse-score.github.io/process_description/main/general_concepts/score_building_blocks_concept.html

with additionally the repositories inside and the mentioned adoptions.

[MaximilianSoerenPollak]

First time I see that picture to be honest, but I will have a look later and see if I can understand.

It is the meta model picture from S-CORE process (which is the the base for the requirements to the docs-as-code) : See https://eclipse-score.github.io/process_description/main/general_concepts/score_building_blocks_concept.html

with additionally the repositories inside and the mentioned adoptions.

I see, ye still seeing this for the first time to be honest. So will have a look.