Nikolaj Berntsen <firstname.lastname@example.org> wrote on 03/15/2006 11:26:57 AM:
> >This is a common problem for people that make this mistake. The
> >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
> >does this, it deletes the .svn metadata folder contained within, and
> >Subversion (not Subclipse) will issue the above message when it tries
> >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?
There are hooks for this already but clearly the build process does not
call them or else that is what would happen. It actually makes sense that
the build process does not call the hooks, as the intent is not really to
delete the items. The problem is just that Subversion happens to have a
method for storing its metadata that is not compatible with this process.
> 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.
How does one identify that a folder is a build dir? This is a
project-specific semantic, it is not a generic concept that Eclipse can
just tell you.
> Btw. I am pretty impressed with the stability and features subclipse has
> accomplished by now.
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Mar 15 17:27:35 2006