Skip to content

Console Launcher should let you specify a module path to scan - #6110

Draft
sormuras wants to merge 3 commits into
mainfrom
sormuras/3836-console-test-module-path
Draft

sormuras wants to merge 3 commits into
mainfrom
sormuras/3836-console-test-module-path

Conversation

@sormuras

Copy link
Copy Markdown
Member

Work in progress...

Addresses:


I hereby agree to the terms of the JUnit Contributor License Agreement.


Definition of Done

Test parent loader for being an instance
of `Closeable` at close-time.

Signed-off-by: Christian Stein <sormuras@gmail.com>
This temporary hook always the console launcher
to register a global module layer for module
scanning.

Signed-off-by: Christian Stein <sormuras@gmail.com>
This commit enabled the JUnit console launcher to
support custom module path entries, similar to the
existing support for `--class-path` entries.

Note that the current iteration re-uses the
`--class-path` option(s) to switch into a modular
testing mode when either `--select-module NAME` or
`--scan-modules` is given at the command-line.

Signed-off-by: Christian Stein <sormuras@gmail.com>
@sormuras sormuras self-assigned this Sep 29, 2026
@sormuras sormuras linked an issue Sep 29, 2026 that may be closed by this pull request
@testlens-app

testlens-app Bot commented Sep 29, 2026

Copy link
Copy Markdown

✅ All tests passed ✅

🏷️ Commit: 3009aa5
▶️ Tests: 41774 executed
⚪️ Checks: 16/16 completed


Learn more about TestLens at testlens.app/docs.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Console Launcher should let you specify a module path to scan

1 participant