Yan Zhang

> Proper evaluation I'd mandatory I understand and appreciate all the work you guys have done. If I remember clearly, some integration tests and details were discussed in a private...

> JDK version: 1.8 It requires JDK 11 now. See https://github.com/redhat-developer/vscode-java/issues/1543#issuecomment-663382692

> not working in if statement nested in for loop At least not due to this, 

@mwaaas This message is probably from buildship, which is a dependency of JDT.LS to deal with Gradle projects: https://github.com/eclipse/buildship/blob/35d01caad3ab023fdd9fdf4a1b9e9c738bff7fd0/org.eclipse.buildship.core/src/main/java/org/eclipse/buildship/core/internal/configuration/GradleProjectValidationResourceDeltaVisitor.java#L112 Adding @cscherryy who is more familiar with Gradle support. BTW I...

released version from marketplace.

> I vaguely remember that I saw at least once the empty beans view There's a known regression issue in dashboard extension v0.7.0 introduced when we were improving the performance....

> But you still observe the issue that you sometimes you get an empty response for beans and mappings, right? Yes, there's some race condition in current impl of dashboard...

From the perspective of a downstream extension, I would expect the result exactly matching with the status of my workspace when `workspace/symbol` request is sent. Same for the coming API...

It was not activated somehow. Check `Log(Extension Host)` for logs about extension activation.

also see: https://github.com/microsoft/vscode-maven/issues/881