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

[Performance] - Import New Project #3302

Closed
mamilic opened this issue Oct 18, 2024 · 6 comments
Closed

[Performance] - Import New Project #3302

mamilic opened this issue Oct 18, 2024 · 6 comments

Comments

@mamilic
Copy link

mamilic commented Oct 18, 2024

When I import large projects, let's take into example spring-boot, I can see in bottom bar the Java notification, and to me it seems like dependecies are downloaded one by one. I am wondering whether that is the case, and could it be somehow parallelized?

@snjeza
Copy link
Contributor

snjeza commented Oct 18, 2024

You may want to take a look at https://docs.gradle.org/current/userguide/performance.html

@mamilic
Copy link
Author

mamilic commented Oct 18, 2024

Thank you @snjeza , will this improve the downloading of dependencies if there is only one module? If I understood correctly this will only allow parallel build if there are multiple modules?

@snjeza
Copy link
Contributor

snjeza commented Oct 18, 2024

You can also review gradle/gradle#28893

@mamilic
Copy link
Author

mamilic commented Oct 20, 2024

Thank you a lot! I just noticed, what will happen in case whe I want the sources to be downloaded, does that happens within jdtls or within respective dependency resolution handler(maven, gradle)?

@rgrunber
Copy link
Contributor

For Maven, it's handled by JDT-LS, and the classpath is updated accordingly See https://github.com/eclipse-jdtls/eclipse.jdt.ls/blob/master/org.eclipse.jdt.ls.core/src/org/eclipse/jdt/ls/core/internal/managers/MavenSourceDownloader.java ). For Gradle, I think that's handles by the Gradle support, which is packaged in JDT-LS. As long as the maven repository, or the gradle repository has published the source artifacts, then it should work.

@mamilic
Copy link
Author

mamilic commented Oct 29, 2024

@rgrunber thank you for the info. This issue can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants