Mark Phippard wrote:
>>SVN Commit: (Error: org.tigris.subversion.javahl.ClientException:
>
> Transaction is out of date
>
>>svn: Commit failed...
>
>
> Congratulations, you have stumbled upon probably the most common problem
> when using Subversion. This is the "mixed-revision" working copy problem.
> When you commit, the revision of the file you committed is updated in your
> WC, but not the revision on the folder. To get it to the HEAD revision,
> you need to run svn update.
>
> The message you got is when trying to delete an item that is not at the
> HEAD revision. You would also get this message if you tried to move/rename
> it or set properties on it.
>
> To fix the problem, run update first, and then commit.
>
> Refer to this section of the book, for a more detailed explanation:
>
> http://svnbook.red-bean.com/en/1.1/ch02s03.html#svn-ch-2-sect-3.1
>
> Mark
>
>
> _____________________________________________________________________________
> Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
> _____________________________________________________________________________
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
>
This is another reason why many users would like to see a working
Synchronize. Or is my presumption that Synchronize will take care of
this wrong?
With CVS in Eclipse, if you attempt to commit without going through
Synchronize, you may be attempting to commit over someone else's commit
and this will also bring on an error message.
Those who are not convinced of Synchronize's utility have, in my
opinion, simply become accustomed to this quirk of Subversion, which is
quite understandable. But Synchronize will, or should, take care of it.
Received on Mon Feb 14 10:16:24 2005