The **wildcard** classPath in `classPaths` configuration only works when `console` is set to `internalConsole`
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- java, typescript, vscode
- Domain
- devtools
Research direction
Start with the launch.json configuration using classPaths, the wildcard path, and the console setting described in the reproduction. Run the supplied normal Java project with internalConsole, integratedTerminal, and externalTerminal, then trace how the debugger handles the classpath in each case; done means wildcard entries load consistently or the supported behavior is documented.
Written by the indexing model from the issue text.
Description
The wildcard classPath in classPaths configuration only works when console is set to internalConsole. Is this a normal situation？
As the image showed, I add custom classpath of plugins with wildcard for my app to load. Howerver it only works when using internalConsole.
Environment
- Operating System: Windows 10 22H2
- JDK version: Oracle JDK 1.8.0_301
- Visual Studio Code version: v1.87.2
- Java extension version: v0.25.15
- Java Debugger extension version: v0.56.2
Steps To Reproduce
- Create normal java project
- In launch.json add some custom classpath in
classPathsconfiguration with wildcard in path. ie${workspaceFolder}/extraCp/* - Add some jar files in extra classpath
- In launch.json set
consoletointernalConsole. - In Main(), get system classloader and print every urls it loads.
- Run Main() and you can see jar files in extra classpath is loaded.
- In launch.json set
consoletointegratedTerminalorexternalTerminal. - Run Main() again and no jar files in extra classpath is loaded.
- Dominant language
- TypeScript
- Stars
- 591
- Forks
- 429
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 19
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode-java-debug
-
ai-triaged enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
microsoft/vscode-java-debug#1689 · 2 comments ·
-
ai-triaged bug
microsoft/vscode-java-debug#1666 · 1 comment · 1 assignee ·
-
ai-triaged bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
microsoft/vscode-java-debug#1658 · 1 comment ·
-
ai-triaged enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/vscode-java-debug#1628 · 3 comments ·
-
Feature support. Openai-triaged enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/vscode-java-debug#1616 · 1 comment ·
All issues in microsoft/vscode-java-debug
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100