-
Notifications
You must be signed in to change notification settings - Fork 406
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
Reopening a gradle project resets its gradle version #1041
base: master
Are you sure you want to change the base?
Conversation
test this please |
The issue can be reproduced in Eclipse too. I have created a workaround. |
So I'm a bit worried that we're setting the gradleHome attribute (as found in the environment variable) to something that doesn't match the gradle version (set by java.import.gradle.version). It doesn't seem to break anything so far but it certainly doesn't feel right |
Checked with Eclipse/Buildship, when a project uses a specific Gradle version or the wrapper, neither
or
Also, it seems the current patch is losing current buildship settings informations. E.g if auto.sync was set to true initially, it's lost. I think the fix should 1st load the buildship settings if they exist, then override their values if necessary and finally save them. |
It doesn't seem to work with buildship 3.1. With a project created in eclipse, overriding workspace default to enable autosync, the buildship core prefs looks like:
When importing the project in vscode, the new content becomes:
|
I still lose the buildship settings when importing the project in a clean workspace :-/ |
@fbricon I have updated the PR. |
Can you please rebase? |
Signed-off-by: Snjezana Peco <[email protected]>
@fbricon I have rebased the PR. |
Fixes redhat-developer/vscode-java#924
Signed-off-by: Snjezana Peco [email protected]