Hi,
I had a similar problem yesterday when I tried to commit for the
first time, after a add to version control, a new project with a very
large amount of files and directories... it freezes my eclipse and when
a kill the javaw.exe process after I reopen eclipse the project was in a
locked state where I had to delete and do everything again (the clean up
didn't helped).
I've tried for 3 times but with the same result... the solution
for me was to divide the commit in 5 parts...
Eclipse 3.2.1
Subclipse 1.1.8 (JavaHL)
Windows XP
SVN server 1.3.2
========================================
Olavo Lira
________________________________________
From: Fournier, Camille F. [mailto:camille.fournier@gs.com]
Sent: Thursday, November 16, 2006 12:15 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
Received on Thu Nov 16 19:51:47 2006