[umaucher]

Fix the Java CLI invocation used by verbose scans.

• Place the SLF4J JVM property before -jar.
• Preserve the required - stdin marker.
• Add regression coverage for the generated command.

Validation: uv run pytest tests/test_main.py (4 passed).
The end-to-end scan reaches Dash successfully; exit code 32 reflects restricted/unverified dependency findings.

[AlexanderLanin]

is this why defaultLogLevel=debug had no effect in the past?

[umaucher]

it had some effect to some extend:

$ dash-license-scan -v ../persistency/score/kvs/tests/test_cases/requirements.txt.lock ../persistency/bazel-persistency/external/score_docs_as_code+/src/requirements.txt
DEBUG:dash_license_scan.main:Starting dash_license_scan.main(None)
[...]

but basically in the end leads to:

DEBUG:dash_license_scan.main:Command: java -jar /home/umaucher/Projects/git/eclipse-score/dash-license-scan/src/dash_license_scan/resources/org.eclipse.dash.licenses-1.1.0.jar -summary /tmp/dash-license-scan-summary-oo9w27ak.txt -Dorg.slf4j.simpleLogger.defaultLogLevel=debug -
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>]

Dash Licenses Summary Output:

"unknow parameter" error 127