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

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.

I am using the synchronize view with compressed folders, and I am committing using the right-click context menu.

Thank you for any help or fixing of this problem.

Best regards,

--
Thomas Jacob, Senior Consultant IT
t.jacob@sinnerschrader.de
T +49.40.398855-832, F +49.40.398855-808
SinnerSchrader Deutschland GmbH
Völckersstraße 38, D-22765 Hamburg
Amtsgericht Hamburg HRB-Nr. 63663
Geschäftsführer: Matthias Schrader (Sprecher), Holger Blank, Laurent Burdin, Thomas Dyckhoff
http://www.sinnerschrader.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org