From: Andreas H. <haf...@in...> - 2010-11-26 15:49:03
|
On 11/26/2010 3:31 PM, Karl Beecher wrote: > Does anyone have any comments on this thread? > > Any volunteers to take a look at a resolution? IDK why but sf.net didn't feel like sending an update notification when I added a comment to the bug, at least I didn't get one. Anyways here it is. <quote> I'll have a look, I'm kinda familiar with that part of the code. I believe we currently simply ignore this case in the code. If the project doesn't exist anymore, we don't send any activities, which means the peers won't notice anything from the deletion. We could try to prevent it, but what if the user didn't delete the project from within Eclipse, but e.g. in Windows Explorer, then did a refresh in Eclipse? Or if another plugin deletes the project? We can't prevent that, but how do we handle it? Leaving the session seems like the easiest way out, except maybe if there are other shared projects in the session. We still shouldn't have the peers copies deleted. </quote> After looking at the code I don't think that it's possible to prevent the deletion. There is a way to do that in Eclipse, but it's only for team providers, and we can't use it. I believe the best we can do is to display a warning "You should leave the session before deleting the project" or "You will leave... " . Andreas |