microsoft / microsoft/vscode-java-test

Use classpath instead of modulepath

Open
#1,611 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ai-triaged enhancement maven test-execution
Dominant language
TypeScript
Stars
340
Forks
173
Avg merge
1d 19h
Merged PRs (30d)
18

Description

Does the Test Runner support switching back to use classpath instead of modulepath?

maven-surefire-plugin has a similar option.

Reference: https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#useModulePath

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how the VS Code Java Test Runner selects modulepath for Java tests, using the Maven Surefire useModulePath reference as the behavior guide. Determine where a classpath switch would belong and verify that Java tests can run and debug with classpath selected without changing the existing default.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, typescript
Domain
testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.