Antranig Basman wrote:
> Very frequently when I move directories around in a Subclipse-managed
> project, on coming to do a subsequent commit I will get an
> "out-of-date" message:
>
> commit -m "Mid-refactoring commit" [file list]
> Deleting workspace/I-RSFComponents/base
> Item is out-of-date
> svn: Commit failed (details follow):
> svn: Item '/projects/RSFComponents/trunk/base' is out of date
>
> This is peculiar since it should be the plugin's job to keep the
> records in the working copy up to date. What is more peculiar is
> that if I then issue an svn update, despite the fact that no
> changes are reported
>
> update -r HEAD E:/workspace/I-RSFComponents
> At revision 2478.
>
> if I then retry exactly the same operation it will then succeed.
> Can anyone explain this behaviour?
>
>
All of this is just how Subversion works, this is not a
Subclipse-specific issue. See this FAQ:
http://subclipse.tigris.org/faq.html#out-of-date
The Synchronize view in the 1.1.x releases has a feature that shows you
these out of date folders as incoming changes so that you know to do an
update.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Nov 23 01:44:39 2006