RE: [Subclipse-users] Commit problems

Hi,

First, using Eclipse 3.2, you should consider upgrading to subclipse 1.1.8 : http://subclipse.tigris.org/callisto.html
I never experienced a problem like you state. How many files were you trying to commit ? I already did it with about 400 and had no problem.

Which adapter are you using (JavaHL or JavaSVN in the preferences) ? (Mark, wouldn't it be possible to ask tigris to install a wiki to group this sort of information ?).
What is you svn server version you're trying to commit on ?

-- Baptiste

-----Original Message-----
From: Fournier, Camille F. [mailto:camille.fournier@gs.com]
Sent: Thu 11/16/2006 6:14 PM
To: users@subclipse.tigris.org
Subject: [Subclipse-users] Commit problems
 
All,

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?

Thanks,
Camille

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org