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

Re: [Subclipse-users] Bug report: Concurrent commits cause inconsistent states

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-11-20 13:43:02 CET

On Nov 20, 2007 4:58 AM, Jacob, Thomas <t.jacob@sinnerschrader.de> wrote:
> Hello dear bug report user group,
> I am experiencing a concurrency problem when using the stable release 1.2.4 of Subclipse, together with Eclipse 3.2.2 (M20070212-1330) (but the Problem may be with any release of Eclipse).
> Committing and updating sometimes takes rather long, and I have turned on the "Run in background automatically" function, so the IDE remains responsive. If I am committing the next set of files while the last commit is still running, this entirely confuses Subclipse and/or SVN, and I receive pseudo-incoming changes and/or conflicts, as well as various error messages.
> CVS synchronisation queues such operations in the process view. I am not familiar with Eclipse internals, but I assume that you require to lock more resources while committing and updating, so that commit operations queue, and concurrent editing of resources currently being committed is prevented as well.

The operations are all queued and synchronized, there are no
concurrency issues. You are seeing the results of the Show Out of
Date folders feature working correctly. See this explanation:


Mark Phippard
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Nov 20 14:05:53 2007

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.