Java will generate false positives and cannot run debugging

[yupor5]

Type: Bug

Discovered false positives in multiple Java projects, unable to run debugging. Need to run mvn clean install first before running debugging

Extension version: 0.58.2
VS Code version: Code 1.99.3 (17baf841131aa23349f217ca7c570c76ee87b957, 2025-04-15T23:18:46.076Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item	Value
CPUs	12th Gen Intel(R) Core(TM) i5-12400 (12 x 2496)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	31.78GB (4.61GB free)
Process Argv	--crash-reporter-id 23564de7-e5d0-44af-bb88-6ccb6ae2cbd9
Screen Reader	no
VM	13%

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dwnewjupytercf:31046870
pythonrstrctxt:31112756
nativeloc1:31192215
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
9064b325:31222308
copilot_t_ci:31222730
e5gg6876:31282496
pythoneinst12:31285622
bgtreat:31268568
4gafe986:31271826
31787653:31262186
3e8i5726:31271747
pythonpulldiag:31298645
996jf627:31283433
pythonrdcb7cf:31303019
usemplatestapi:31297334
7bj51361:31289155
747dc170:31275177
aj496949:31278748
pylancecolor:31303816
aj953862:31281341
generatesymbolt:31295002
convertfstringf:31295003
gendocf:31295004

[shaestha]

Extension version: 0.58.90

[github-actions]

Hi @yupor5, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

Suggestions to ensure up‐to‐date classes and enable debugging without manual mvn calls:

• Add a preLaunchTask in your launch.json to compile before launch. Example:

  // .vscode/launch.json
  {
    "version": "0.2.0",
    "configurations": [
      {
        "type": "java",
        "name": "Debug Current File",
        "request": "launch",
        "mainClass": "${file}",
        "preLaunchTask": "mvn compile"
      }
    ]
  }

• Define the Maven task in .vscode/tasks.json:

  // .vscode/tasks.json
  {
    "version": "2.0.0",
    "tasks": [
      {
        "label": "mvn compile",
        "type": "shell",
        "command": "mvn clean compile",
        "problemMatcher": ["$maven-compile"]
      }
    ]
  }

• Use the Java and Maven commands in VS Code Command Palette:
  • “Maven: Update Project” to sync dependencies and recompile
  • “Java: Clean the Java language server workspace” to clear stale errors

• Ensure your workspace settings point to the Maven output folder:

  // settings.json
  {
    "java.project.outputPath": "${workspaceFolder}/target/classes",
    "java.project.referencedLibraries": [
      "${workspaceFolder}/target/*.jar"
    ]
  }

Other references worth checking:

Other references with low confidence

• Cannot debug tests, getting … (debugging tests fails; suggests enabling logging and ensuring tests are compiled first): Cannot debug tests, getting  #999
• Unable to Debug On Vscode (no debug button; logs show decompiler errors): Unable to Debug On Vscode  #1385
• java debug console code completion (console completion in debug mode): java debug console code completion #817

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!