Re: again: overwriting resource -> deleted and not modified

> Maybe it is possible to workaround this bug? For example if Eclipse
> indicates the file is deleted, check if the file exists, if so it is
> either overwritten by the same version or by a different version. If it
> does not exist then it's really deleted.

It doesn't work that way. Eclipse just tells us the name of a file to be
deleted. It doesn't tell us anything else. We can then delete it by
running svn delete and telling Eclipse that we handled it.

If this is something you do a lot, there is a workaround in the next
release of Subclipse. Add an SVN Property named "DeferFileDelete" with a
value = "true" on the parent folder of these JAR's. When this property is
set, we will not run svn delete. This should cause the file to just show
as being modified.

Thanks for figuring out when this happens. I usually do not use this
method, but I do occasionally. That explains why I only see the problem
occasionally.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Sun Nov 27 01:53:41 2005