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

[Subclipse-users] Commit problems

From: Fournier, Camille F. <camille.fournier_at_gs.com>
Date: 2006-11-16 18:14:45 CET


We've been having some problems with committing via subclipse that I
can't find any issue reports or emails on. Today one of our developers
(using subclipse 1.0.3, windows, Eclipse 3.2) tried to commit a large
set of changes. He claims that he verified that all the files he
selected to commit were checked in the commit dialogue. After
committing, all of these changes disappeared from his outgoing view, but
six of the files did not actually successfully commit, and he did not
realize this until an hour later. Is this a known problem? From our
perspective, a user should not have to fully resynchronize (which takes
about 20 minutes) to detect that a checkin only partially succeeded--
either it should fully fail, or the files that did not actually get
committed should remain in the outgoing view. We've always seen this
problem with new files which are sometimes not checked in the commit
dialogue but still disappear from the outgoing after committing.
Any advice?

Received on Thu Nov 16 18:15:54 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.