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

Unable to save settings if .ijwb already exists #434

Closed
hmemcpy opened this issue Nov 5, 2018 · 2 comments · Fixed by #6839
Closed

Unable to save settings if .ijwb already exists #434

hmemcpy opened this issue Nov 5, 2018 · 2 comments · Fixed by #6839

Comments

@hmemcpy
Copy link

hmemcpy commented Nov 5, 2018

image

This happens when attempting to import (from scratch) a bazel project that may already contain a .ijwd directory.

This is a regression, this used to work fine if .project was already present.

@chaoren
Copy link
Collaborator

chaoren commented Nov 5, 2018

We decided that was not a desirable feature, because it nukes your existing project data. If you really want this you should manually delete the existing directory, or name the new directory something else.

@chaoren chaoren closed this as completed Nov 5, 2018
@joprice
Copy link

joprice commented Jan 2, 2020

@hmemcpy I found that you can put the .bazelproject elsewhere in your tree, and import it using the wizard, and it will generate an import statement to the other file. That way, you can wipe away the .ijwd dir, even with local changes to the .bazelproject file, and re-import.

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 a pull request may close this issue.

3 participants