[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Would like to disable Automatic SVN Delete on Eclipse file delete

From: Aaron Digulla <digulla_at_hepe.com>
Date: 2006-05-02 12:24:18 CEST

Ben Huchison wrote:
> There appears to be some behaviour in Subclipse that triggers a SVN
> Delete operation when one does a file delete in Eclipse. I would like to
> disable this functionality, as there are often times when I would like
> to delete a working copy file but without creating a pending SVN Delete.
> The main motiviation I encounter is the build system where I work
> requires me to overwrite versioned JAR files from one project into
> another. When I do this from Eclipse, the file gets marked as Deleted,
> which is not what I want.
> Should I file a feature request for this?

This is probably an Eclipse+Subclipse issue. I have the same problem
when I drag&drop a new version of a JAR into a project. Afterwards,
Subclipse will try to delete the file in the repository and there is no
easy way to get out of that.

But when you say "overwrite versioned JAR files" do you mean that your
build process just overwrites the file (ie. outside of Eclipse's
control), then Eclipse notices that the file has changed and finally,
Subclipse wants to delete it?

That would mean that updating a file from "outside" of Eclipse triggers
a chain of events which Subclipse doesn't or cannot handle correctly.
Maybe Eclipse first sends a delete event and then a "new/add file" event
which Subclipse ignores because it wants to commit the delete, first.


Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue May 2 12:26:32 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.