Skip to content

Conversation

@RolandJentschETAS
Copy link
Contributor

@RolandJentschETAS RolandJentschETAS commented Jan 20, 2026

📌 Description

fix issues which prevent latest main update.
Otherwise integration fails (bazel run //:docs_combo_experimental does not run)

🚨 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
Copy link

github-actions bot commented Jan 20, 2026

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: 6b1b4520-e0c3-436e-866d-92bcb0a91638
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
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 (73 packages loaded, 9 targets configured)

Analyzing: target //src:license-check (126 packages loaded, 1686 targets configured)

Analyzing: target //src:license-check (134 packages loaded, 2484 targets configured)

INFO: Analyzed target //src:license-check (137 packages loaded, 4500 targets configured).
[4 / 12] Creating runfiles tree bazel-out/k8-opt-exec-ST-d57f47055a04/bin/external/score_tooling+/dash/tool/formatters/dash_format_converter.runfiles [for tool]; 0s local
INFO: Found 1 target...
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: 14.918s, Critical Path: 0.44s
INFO: 13 processes: 4 disk cache hit, 9 internal.
INFO: Build completed successfully, 13 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
Copy link

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

gd_req__impl_design_code_link,

Docs-as-Code shall allow source code to link to needs.
Docs-as-Code shall allow source code to link to requirement needs.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It can be any need though, right? Tests, requirements, documents etc.
So I guess maybe better to say Sphinx-Needs ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, at this place (from the upper layer linked requirement gd_req__req_attr_impl) only requirements need to be linked.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add sphinx needs to text before requirement mentioned

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would keep it as is to be honest. We intentionally said "needs" here, as our tool supports more than the process requires.

Copy link
Contributor

@MaximilianSoerenPollak MaximilianSoerenPollak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just two quick comments.

Though they can also be fixed in future PR.

Update documentation to specify 'sphinx-needs' for linked requirements.

Signed-off-by: RolandJentschETAS <[email protected]>
Removed commented-out req-Id section from metamodel.yaml.

Signed-off-by: RolandJentschETAS <[email protected]>
.. :satisfies: gd_req__impl_dynamic_diagram
Provide needs type ``dd_dyn`` for dynamic diagrams showing unit interactions as UML.
.. Provide needs type ``dd_dyn`` for dynamic diagrams showing unit interactions as UML.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commenting is not a good idea. Delete it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See below

parts: 3

# req-Id: tool_req__docs_dd_dyn
dd_dyn:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If there is no requirement for the dd_dyn element, shouldn't we delete it from the metamodel?

Copy link
Contributor Author

@RolandJentschETAS RolandJentschETAS Jan 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem is, that the process description of the implementation process still contains a dynamic diagram, but the process requirement is gone. So it is currently unclear if deletion of the requirement was a mistake or not. The PR is only to make overall update is running. But it don't solve the issue, that the implementation process contains undefined parts. But this is in another repo and must be fixed after discussion.

@a-zw a-zw mentioned this pull request Jan 20, 2026
6 tasks
Copy link
Member

@AlexanderLanin AlexanderLanin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Open points remain relevant; and please do address them!
However they can equally well be addressed post merge, so I'm merging this now.

gd_req__impl_design_code_link,

Docs-as-Code shall allow source code to link to needs.
Docs-as-Code shall allow source code to link to requirement sphinx-needs objects.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would keep this as it was, since our tool requirement intentionally did not differentiate whether its a requirement or not. The tool was more generic, then the minimum process requirement.

@AlexanderLanin AlexanderLanin merged commit d9f95fd into eclipse-score:main Jan 20, 2026
10 checks passed
@AlexanderLanin AlexanderLanin deleted the fix_latest_main_update branch January 20, 2026 17:35
@github-project-automation github-project-automation bot moved this from Draft to Done in Infrastructure Jan 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants