Andy Xu(devdiv)

I can reproduce this bug, the generated .project refers old file path and doesn't update C:\Users\XXX\AppData\Roaming\Code\User\workspaceStorage\XXX\redhat.java\jdt_ws\jdt.ls-java-project\.project ``` jdt.ls-java-project org.eclipse.jdt.core.javabuilder org.eclipse.jdt.core.javanature src/Hello.java 1 c:/work/example/SimpleJava/Hello.java ``` It refers old java file `c:/work/example/SimpleJava/Hello.java`...

ADD @yhtsao for the original reporter

Investigating on this strange problem, will post the result later

@haraldatbmw Sorry to tell you that: currently , ASE is not supported by maven tooling.

Sorry @mmzh , we don't support ASE and yet there is no plan to support it in the near future.

We cannot help since our dependency azure java sdk have version conflictions: see this issue: https://github.com/Azure/azure-sdk-for-java/issues/14898

Hi @alexandrospanagiotidis, we have already solve this issue by adopting azure-identity, could you please take a try again.

Thank you very much for the advice, please keep on looking the milestone for the scheduled dev plan and progress.

@mojo2012 Thanks for using vscode java debugger, which also supports HCR just the same as that in eclipse, if you prefer DCEVM, which is not tested by us yet, we...

That is possibly caused by we hint vscode a cheap local scope https://github.com/Microsoft/java-debug/blob/master/com.microsoft.java.debug.core/src/main/java/com/microsoft/java/debug/core/adapter/handler/ScopesRequestHandler.java#L50 We can hint vscode expensive fetching on attach mode.