>This is a common problem for people that make this mistake. The problem
>when you get your build folder versioned is that when Eclipse does a
>complete build it will just delete this folder and recreate it. When it
>does this, it deletes the .svn metadata folder contained within, and then
>Subversion (not Subclipse) will issue the above message when it tries to
>do something with that folder and cannot find its metadata.
>
>
I have been there too. Seing this thread made me wonder if its not
possible to do some eclipse magic such that if a folder contains a .svn
directory, it cannot just delete it, it would always svn delete it? I
mean if the user does a delete it is caught and issued as a svn delete.
Is it impossible to something similar to the automatics build deletes?
Alternatively would it be possible to make hooks such that the user is
issued a strongly worded warning if the build dir is added to subversion
control, of if the build dir is changed to another directory which is
already under subversion control.
Btw. I am pretty impressed with the stability and features subclipse has
accomplished by now.
Cheers,
/\/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Mar 15 17:23:36 2006