The process is launched twice in debug mode.

[tcouery-ltr]

Describe the bug
Since v0.45.0 version when I launch a maven task 2 process are launch : 1 in debug mode and 1 in normal mode. In the case of jetty:run, the debug process cannot work because the port is already open by the first process.
It works in Run mode, and it works with version 0.44.0

To Reproduce
Steps to reproduce the behavior:

1. Go to a task a Debug the task
2. Check the process

Expected behavior
I expect to have only one process running.

Environments (please complete the following information as much as possible):

• OS: Windows 11 and Linux
• VS Code version: 1.106.2
• Extension version 0.45.0

Screenshots
First process:
"java.exe" -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=56641 -classpath "....\plexus-classworlds-2.7.0.jar" "-Dclassworlds.conf=...\m2.conf" "-Dmaven.home=...\apache-maven-3.9.6" "-Dlibrary.jansi.path=...\jansi-native" "-Dmaven.multiModuleProjectDirectory=...\project" org.codehaus.plexus.classworlds.launcher.Launcher jetty:run -f ....\pom.xml

Second process
"java.exe" -classpath "...\plexus-classworlds-2.7.0.jar" "-Dclassworlds.conf=...\m2.conf" "-Dmaven.home=...\apache-maven-3.9.6" "-Dlibrary.jansi.path=...\jansi-native" "-Dmaven.multiModuleProjectDirectory=...\project" org.codehaus.plexus.classworlds.launcher.Launcher jetty:run -f ....\pom.xml

[github-actions]

Hi @tcouery-ltr, 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.

The double-launch is a regression in Maven for Java 0.45.0 when debugging Maven goals (e.g. jetty:run). Here are a few workarounds until an upstream fix is published:

• Roll back to Maven for Java v0.44.0, where this issue doesn’t occur.
• Switch to a “run then attach” approach:
  • In .vscode/tasks.json, define a preLaunchTask that uses mvnDebug jetty:run.
  • In .vscode/launch.json, use a Java attach configuration on the debug port (8000 by default).
  • This way only the debug-enabled process is launched, and VS Code attaches without spawning a second JVM.
• Alternatively, manually invoke mvnDebug jetty:run in a terminal, then attach via a Java Debug (Attach) launch configuration.

No existing GitHub issue exactly matches this behavior, so please file a new one if you need a tracked fix.

Other references with low confidence

• Support running command before attaching debugger (0.11.0 Plan #120): demonstrates using preLaunchTask with mvnDebug, though it requires clicking Debug twice.
  Support running command before attaching debugger vscode-java-debug#120 (comment)

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!