Fournier, Camille F. wrote:
>
> 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.
>
It is not possible to have a partial commit, unless these files are
spread across multiple projects. It just cannot happen at the
Subversion level. There have been some UI issues in the past,
particularly when using the Synchronize view, which would make it easy
for a developer to do a commit, followed by an update, where the latter
"backdates" their working copy. This would make it appear, looking at
the local files, that certain changes were missiing.
svn log and svn diff should allow you to verify what was in the commit.
Since you are using Eclipse 3.2, I'd strongly recommend that you install
Subclipse 1.1.8.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Nov 16 19:58:53 2006