-
Notifications
You must be signed in to change notification settings - Fork 170
-
Notifications
You must be signed in to change notification settings - Fork 170
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
Buildship falling over on "out of sync" projects #478
Comments
Step 2 is unnecessary, Buildship already does a full refresh as part of synchronization. Is there a chance you could provide a reproducible example project? |
I will try, however in the coming few weeks in particular I may have trouble finding spare time (between end-of-school year events, some travel, and of course work commitments). |
Due to inactivity, I'm going to close this issue. Feel free to reopen it if there's an update. |
I also have this issue which seems to appear on subprojects of my multi-module projects. Closing/re-openning the projects is a workaround as said in the OP. The stack trace is: |
I've hit the following error dialog a number of times now:
I think a factor is having recently git-switched branches. (Which I do externally in a command shell.) Switching branches usually adds or removes one module, so I have learned to follow these steps:
./gradlew generateSources
(in command shell)After doing this, sometimes the error mentioned above will appear in 4 or 5 projects. I'm not sure why. The .project files are not git versioned, so they shouldn't have changed. (Nothing should change them except Eclipse.)
One workaround is to close and reopen each project (getting Gradle to refresh each time to step to the next one). This gets tedious, so sometimes I instead do
./gradlew cleanEclipse
to delete all the .project files, then steps 2 & 3 again, which seems to fix it up.Is there any way to encourage Eclipse to refresh its own Project, before Gradle proceeds to twiddle it?
Versions:
Full stack trace:
The text was updated successfully, but these errors were encountered: