Skip to content
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

Closed
martinlippert opened this issue Nov 20, 2017 · 2 comments · Fixed by #459
Closed

improve startup performance for gradle projects in workspace #451

martinlippert opened this issue Nov 20, 2017 · 2 comments · Fixed by #459

Comments

@martinlippert
Copy link

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://github.com/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).

@mickaelistria
Copy link
Contributor

Is the performance comparable to the one with BuildShip in Eclipse IDE or is it worse with JDT-LS?

@fbricon
Copy link
Contributor

fbricon commented Nov 20, 2017

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.

@fbricon fbricon added this to the End November 2017 milestone Nov 30, 2017
snjeza added a commit to snjeza/eclipse.jdt.ls that referenced this issue Aug 23, 2021
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 <snjezana.peco@redhat.com>
snjeza added a commit that referenced this issue Aug 23, 2021
a regression of #451

Signed-off-by: Snjezana Peco <snjezana.peco@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants