!Important Gradle daemon view only show part of all Gradle Deamon JVM

[mozhuanzuojing]

Extension Name: vscode-gradle
Extension Version:3.6.1
OS Version:window10
VSCode version: 1.60.0-insider (system setup)

Describe the bug

When I open the gradle deamon view and wait a few seconds. Execute jps -l -m -v to see two Deamon. But Gradle Deamon View can only see one.

One of the Gradle Deamon JVMs is started by the vscode-java plugin, Another Gradle Deamon JVM is started by the vscode-gradle plugin. But both Deamon are analyzing the same project! Repeat it!

To Reproduce

1. Open a gradle project
2. Await build job finished
3. Open gradle deamon view

Expected behavior
Show all current gradle deamon jvm of running.

Screenshots

Output from "Gradle Tasks"

Does the bug still exist if you disable all other extensions?
Yes

Additional context

When opening the Gradle view, if you find Gradle Deamon exists in the current project, do not start a new Gradle Deamon. Because it is repetitive, and it will waste a lot of time.

[CsCherrYY]

@mozhuanzuojing Could you try to click Refresh Daemon Status button? Does it work?

[mozhuanzuojing]

@CsCherrYY

• No display after clicking refresh

[mozhuanzuojing]

@CsCherrYY I re-describe the issue.

A serious problem was found. The vscode-java plugin starts a Gradle Deamon JVM. Then I executed Gradle Task from the Gradle view, it restarted a new Gradle Deamon JVM！

[mozhuanzuojing]

@CsCherrYY I hope that the next version can reuse the existing Gradle Deamon. Because I don't want to wait for the project to compile. And reduce calls to Java: Update Project. Thanks.

[CsCherrYY]

@mozhuanzuojing That's also what we want to improve in the future 😄. vscode-gradle could have a better way to collaborate with vscode-java.

[mozhuanzuojing]

Duplicate of #953

[CsCherrYY]

tracked in #953 and will be in Jan 2022 milestone.