> Is there any (easy) way confirm that this is either an Eclipse or
> bug? It's really annoying because now I have to revert the overwrite,
It seems like it has to be a Subclipse bug because it is not consistent. I
have been doing this in Eclipse 3.0 recently and have not been having the
It still seems that it must be an Eclipse bug, I just cannot see how. Here
is why. In theory, I think the only code we have that does an svn delete
is the MoveDeleteHook. Eclipse is responsible for calling this hook, not
us. If Eclipse is calling it when it shouldn't, then it is their bug. It
should just be a normal file update scenario where our code is not
triggered at all, other than our ResourceChangeListener to update our
You can try checking out our core and ui projects and searching for the
calls to svn delete. Maybe there is another scenario I am not aware of.
But if it is the MoveDeleteHook, then it is an Eclipse bug. Also, if it is
the MoveDeleteHook, then I have a change in trunk where you can tell
Subclipse to ignore deletes. You can then manually do the delete at commit
time if the file is still "missing".
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
Received on Sat Nov 26 09:46:14 2005