You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When opening a standalone java file, we 1st link it to the default Java project in JDTUtils.getFakeCompilationUnit. The link is performed in a workspace job, but JDTUtils.getFakeCompilationUnit is already called within a IWorkspaceRunnable, in DocumentLifeCycleHandler.didOpen.
So by the time JDTUtils.getFakeCompilationUnit returns, the resource has not been actually linked yet, because the linking job hasn't run, which causes diagnostics to return the uri of the linked resource, not the one from the actual file
The text was updated successfully, but these errors were encountered:
When opening a standalone java file, we 1st link it to the default Java project in JDTUtils.getFakeCompilationUnit. The link is performed in a workspace job, but JDTUtils.getFakeCompilationUnit is already called within a IWorkspaceRunnable, in DocumentLifeCycleHandler.didOpen.
So by the time JDTUtils.getFakeCompilationUnit returns, the resource has not been actually linked yet, because the linking job hasn't run, which causes diagnostics to return the uri of the linked resource, not the one from the actual file
The text was updated successfully, but these errors were encountered: