-
Notifications
You must be signed in to change notification settings - Fork 399
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve startup performance for gradle projects in workspace #451
Comments
Is the performance comparable to the one with BuildShip in Eclipse IDE or is it worse with JDT-LS? |
Seems like Eclipse is much faster to restart. I believe what kills us is we're eagerly trying to re-import/synchronize the gradle project state after the server restarts, even if it already exists in the workspace, which eclipse doesn't do. |
snjeza
added a commit
to snjeza/eclipse.jdt.ls
that referenced
this issue
Aug 23, 2021
a regression of eclipse-jdtls#451
snjeza
added a commit
to snjeza/eclipse.jdt.ls
that referenced
this issue
Aug 23, 2021
a regression of eclipse-jdtls#451 Signed-off-by: Snjezana Peco <[email protected]>
snjeza
added a commit
that referenced
this issue
Aug 23, 2021
a regression of #451 Signed-off-by: Snjezana Peco <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems to still take quite some time to get the jdt.ls to respond to workspace symbol requests if you open a workspace with some gradle projects inside.
I use this for testing:
https:/spring-io/sagan
Woud be great to get startup performance improvements for Gradle projects (in the same way than it got implemented for Maven projects).
The text was updated successfully, but these errors were encountered: