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

Add buildship auto sync preference #2224

Merged
merged 1 commit into from
Sep 16, 2022
Merged

Conversation

snjeza
Copy link
Contributor

@snjeza snjeza commented Sep 13, 2022

Fixes redhat-developer/vscode-java#2673

Signed-off-by: Snjezana Peco snjezana.peco@redhat.com

@CsCherrYY
Copy link
Contributor

I'm curious what's the difference between this one and the currrent configuraiton java.configuration.updateBuildConfiguration for Gradle projects, will they do the similar thing?

@testforstephen
Copy link
Contributor

I'm curious what's the difference between this one and the currrent configuraiton java.configuration.updateBuildConfiguration for Gradle projects, will they do the similar thing?

+1

@snjeza
Copy link
Contributor Author

snjeza commented Sep 14, 2022

I'm curious what's the difference between this one and the currrent configuraiton java.configuration.updateBuildConfiguration for Gradle projects, will they do the similar thing?

You are right. They do the similar thing. See redhat-developer/vscode-java#2673 (comment)
We could still add this property if a user moves a project from Eclipse with auto.sync=true. VS Code shouldn't update org.eclipse.buildship.core.prefs

@CsCherrYY
Copy link
Contributor

Get it. My point is if we can just use the value of java.configuration.updateBuildConfiguration to set auto.sync of buildship configuration (if it works)? In this way we can avoid adding a new VS Code configuration and making users confused due to multiple "sync" configurations.

@snjeza
Copy link
Contributor Author

snjeza commented Sep 15, 2022

My point is if we can just use the value of java.configuration.updateBuildConfiguration to set auto.sync of buildship configuration (if it works)?

We can set auto.sync to true if java.configuration.updateBuildConfiguration = automtatic

@snjeza snjeza changed the title Add buildship auto sync preference [WIP] Add buildship auto sync preference Sep 15, 2022
@CsCherrYY
Copy link
Contributor

We can set auto.sync to true if java.configuration.updateBuildConfiguration = automtatic

Sounds great. In this way, if a user set java.configuration.updateBuildConfiguration to automatic and we also set auto.sync to true, will the buildship synchorize the project twice? (the first one comes from auto.sync and the second one from language server) Or jdtls/buildhsip side has some mechanisms to prevent this?

@snjeza
Copy link
Contributor Author

snjeza commented Sep 15, 2022

will the buildship synchorize the project twice? (the first one comes from auto.sync and the second one from language server) Or jdtls/buildhsip side has some mechanisms to prevent this?

I will check.
I have fixed it. See 6474013#diff-f23d0258ce24117c110acd6753e8490a09fbdf0bc039d662bdffe279c8c28469R242

Signed-off-by: Snjezana Peco <snjezana.peco@redhat.com>
@snjeza snjeza changed the title [WIP] Add buildship auto sync preference Add buildship auto sync preference Sep 15, 2022
Copy link
Contributor

@CsCherrYY CsCherrYY left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@snjeza snjeza merged commit dbd035c into eclipse-jdtls:master Sep 16, 2022
@rgrunber rgrunber added this to the End September milestone Sep 28, 2022
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

Successfully merging this pull request may close these issues.

Add buildship auto sync preference
4 participants