|
From: Colin S. <col...@ex...> - 2005-01-04 15:35:43
|
I get the exact same behaviour with Eclipse 3.1M4, and I do remember getting it with 3.0.1 as well. It's indeed quite annoying, and happens inconsistently. It will happen a lot of the time, but not all the time. As you mention, the commits always in fact work, but Eclipse just doesn't seem to be able to get the confirmation when the problem happens, and setting a longer timeout in Eclipse makes no difference... This is of course using SSH for accessing SourceForge. I do not get any similar errors when I use TortoiseCVS from Windows Ecplorer. I have not tried switching from Eclipse's buil-in SSH support to external (pointing to putty), but I might try that soon to see if it works better. Juergen Hoeller wrote: >Odd... Rod mentioned something similar recently. I can just repeat what I >said to him: Everything works nicely for me in IntelliJ IDEA. I haven't had >any problems with SourceForge CVS in the past 6 months or so. Of course CVS >operations often take a while, but I always get clean results on first >attempt. > >Juergen > > >-----Original Message----- >From: spr...@li... >[mailto:spr...@li...]On Behalf >Of Darren Davison >Sent: Tuesday, January 04, 2005 12:09 PM >To: spr...@li... >Subject: [Springframework-developer] CVS commits from Eclipse > > > >Is anyone else having trouble committing to CVS from Eclipse? I >consistently >get IO errors waiting for confirmations. The commits always seem to succeed >but it leaves me with a false conflict in the eclipse workspace on every >file >in the previous commit. It's happenning to me on 2 different boxes, one >running eclipse 3.0.1 on Linux and one running WSAD 5.1.2 on Windoze. > >Annoying. > >(Happy New Year all) > >-- >Darren Davison >Public Key: #DD356B0D > > |