We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When workspace is reopened, we always update Maven project configurations, which is CPU and Memory inefficient (see eclipse-che/che#8335 (comment)).
We basically need to implement : https://github.com/eclipse/eclipse.jdt.ls/blob/f08b7c215d7e03597f5f0a91ac91380c90c9787e/org.eclipse.jdt.ls.core/src/org/eclipse/jdt/ls/core/internal/managers/MavenProjectImporter.java#L189-L192
I think, one way to do it it to check if the project pom.xml is more recent than the last workspace serialized state file.
The text was updated successfully, but these errors were encountered:
fbricon
No branches or pull requests
When workspace is reopened, we always update Maven project configurations, which is CPU and Memory inefficient (see eclipse-che/che#8335 (comment)).
We basically need to implement : https://github.com/eclipse/eclipse.jdt.ls/blob/f08b7c215d7e03597f5f0a91ac91380c90c9787e/org.eclipse.jdt.ls.core/src/org/eclipse/jdt/ls/core/internal/managers/MavenProjectImporter.java#L189-L192
I think, one way to do it it to check if the project pom.xml is more recent than the last workspace serialized state file.
The text was updated successfully, but these errors were encountered: