On Nov 20, 2007 5:06 AM, Jacob, Thomas <t.jacob@sinnerschrader.de> wrote:
> Hello dear bug report user group,
>
> I am experiencing a problem when using the stable release 1.2.4 of Subclipse, together with Eclipse 3.2.2 (M20070212-1330) (but the Problem may be with any release of Eclipse).
>
> When removing a file in the navigator view using "delete", and then readding the file by creating it or renaming another one to take its place, the resource still appears as deletion, and I am not able to commit it.
>
> The CVS synchronisation and TortoiseSVN behave differently, and I think this is more sensible. When deleting a resource, it shows up as outgoing deletion. When putting a resource at the place of the deleted one, it shows up as outgoing change, silently readding the file in the local svn information.
>
> The situation happens quite often, as you often get a file from a customer as a replacement for an existing one, but the file name does not match. So you copy the correct file name, delete the old file in Eclipse, put the new one into the directory and paste the file name, renaming the new file to the name of the old one. This works in Explorer, but leaves Subclipse in a state where I have to remove the file once again and put it into the folder once again.
The difference is that neither Explorer nor TortoiseSVN intercept
deletes/moves and relay them to SVN. You can set a property on your
project to ignore deletes and then we will do the same. Most people
want this behavior.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Nov 20 13:53:56 2007