>>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
and you know to not be a bug? (has it been raised with the JDT people)?
>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.
CVS would have the same incompatibility (the CVS dir), would it not?
>>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.
Yes, it is something sitting on a java project. Aren't there extension
points, or the like, allowing one to get a call back once project
properties are changed? Then one could validate the sanity there?
Something like (very naively), at SVN hookup-of-the-project time:
if getProject().getnature() == java
or at add directory time:
if getProject.getnature() == java
if dir == getProject().getproperties().get("build dir") issueWarning();
I'll say it again: very naively ;-)
>>Btw. I am pretty impressed with the stability and features subclipse has
>>accomplished by now.
And with the support and responsivity you offer O:-)
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Mar 15 17:41:43 2006