Schema documentation

[SimonKozik]

This pull request followup on #88 and provide documentation for JSON schema.

Part of #38

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.4.2) and connecting to it...
INFO: Invocation ID: b4049baf-aeab-41eb-8f59-0516133ea857
Computing main repo mapping: 
Computing main repo mapping: 
WARNING: For repository 'rules_python', the root module requires module version rules_python@1.8.3, but got rules_python@1.8.5 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'rules_cc', the root module requires module version rules_cc@0.2.16, but got rules_cc@0.2.17 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'score_tooling', the root module requires module version score_tooling@1.1.0, but got score_tooling@1.1.2 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'score_rust_policies', the root module requires module version score_rust_policies@0.0.3, but got score_rust_policies@0.0.5 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)

Analyzing: target //:license-check (47 packages loaded, 10 targets configured)

Analyzing: target //:license-check (117 packages loaded, 198 targets configured)

Analyzing: target //:license-check (151 packages loaded, 3500 targets configured)

Analyzing: target //:license-check (152 packages loaded, 7637 targets configured)

Analyzing: target //:license-check (163 packages loaded, 7899 targets configured)

Analyzing: target //:license-check (163 packages loaded, 7899 targets configured)

Analyzing: target //:license-check (167 packages loaded, 9911 targets configured)

INFO: Analyzed target //:license-check (168 packages loaded, 10037 targets configured).
[12 / 16] JavaToolchainCompileClasses external/rules_java+/toolchains/platformclasspath_classes; 0s disk-cache, processwrapper-sandbox
[14 / 16] JavaToolchainCompileBootClasspath external/rules_java+/toolchains/platformclasspath.jar; 0s disk-cache, processwrapper-sandbox
[15 / 16] Building license.check.license_check.jar (); 0s disk-cache, multiplex-worker
INFO: Found 1 target...
Target //:license.check.license_check up-to-date:
  bazel-bin/license.check.license_check
  bazel-bin/license.check.license_check.jar
INFO: Elapsed time: 22.630s, Critical Path: 2.55s
INFO: 16 processes: 12 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 16 total actions
INFO: Running command line: bazel-bin/license.check.license_check ./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

[MaciejKaszynski]

looks good

[paulquiring]

Very concise and detailed. One comment: I feel that someone without prior knowledge of this topic would need a bit more information. I left a proposal in the comments.

[paulquiring]

I get the feeling that someone with no prior knowledge of this topic would need a little more information.

Just adding one more paragraph and moving around the paragraphs, would help.

1. Run Targets: Grouping and Components Activation -> Run Targets: Modelling the system
   Explain active, (un)assigned

2. Right after "When the Launch Manager Starts a Component" you could move "Run Targets: Grouping and Components Activation" as is.

[SimonKozik]

Changes applied, finger cross it reads better now and is more understandable.

[NicolasFussberger]

Please consider this comment from @pawelrutkaq #110 (comment)

lets remove s-core from name. makse no sens imho. and it even wors with - and _ mixup