Community
Participate
Working Groups
build I20030806 What I did : 1- launch the last integration build on my current workspace. My workspace contained the debug (org.eclipse.debug.*, org.eclipse.jdt.debug.*, org.eclipse.jdt.launching.*) and org.eclipse.jface.text plug-ins from the cvs, the other required plug-ins imported as binary plug-ins. 2- opened the preferences of the synchronized view. Checked all check boxes. 3- clicked of the toolbar view button to performed "refresh with remote". The synchronization started in the background. 4- as I was able to do something else while it was synchronizing, I replaced the old binary plug-ins by the new one from the last integration build (with import > external plug-ins and fragments). I also replaced the cvs version of org.eclipse.jface.text by the binary version (I had no more use of the cvs version, the changes I needed are in the new version). I think that was what triggered the error. The import action finished before the synchronization, and after some time, the synchronization process stopped, with an error message in the progress view : An error occured while synchronizing with remote contents. Error retrieving remote resource tree for /org.eclipse.jface.text. Parent is not managed by CVS.
Basically one of the projects that was a candidate for synchronizing was no longer under CVS control at the time the background job was run. The message is shown to confirm that state had changed since you asked to synchronize and one of the projects wasn't sync'd. Since you manually replace the project the error message should make sense in the context of the actions you took after starting the background sync. Please tell me what you would of expected to occur in this situation?
I think that the synchronization shouldn't failed in this case. One part of the request in no more valid, but the rest is still ok. It should display the error and continue.
It does continue. If one project has an error synchronizing it records the error and continues with the others. I've just tried this and it continues for me. What made you think that it didn't continue?
Verify for M3 that an error with one project allows the refresh to continue for the other projects.
The Team background job continues refreshing subscribers, however, the CVS TeamSubscribers don't continue refreshing if one resource fails. A fix would require re-writting the refresh operations to accept IStatus object so that warnings can be reported back to the user but that the operation can still continue.
This was fixed a long time ago
