-
Notifications
You must be signed in to change notification settings - Fork 104
Open
Description
Describe the bug
When i debug a maven based java application in VSCode the dependencies which are defined in the "test-scope" are not loaded and therefore it is not possible to debug an application when a component is needed which is marked for the test-scope. A workaround is to remove the test-scope, but then it is also part of my productive deployment which is not my goal. Another workaround is probably using maven profiles. But this increased the complexity.
To Reproduce
Steps to reproduce the behavior:
- Create a maven based project
- Create the H2 dependeny with scope test e.g.
Expected behavior
A switch/option/setting to define the maven scope when debugging an application.
Environments (please complete the following information as much as possible):
- OS: Windows 10
- VS Code version: 1.48.2
- Extension version Java extension pack 0.10.0
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels