Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
ok, maybe Eclipse is not the latest version available but this is because we follow the productline of IBM's WebSphere Development tools (WDSCi in our case). And, as with many IBM tools, they alway's are a bit behind with the versions comparing to the existing versions (Sun, Eclipse,...) Nevertheless, we are running IBM's latest version of WDSCi (available from IBM Belgium) and (at least on 2 dev-pc's) have installed latest fixes/fixpacks etc... This includes Eclipse 3.0.x Meanwhile I found the solution to my problem: As David Somers said: "check "respond as cvs 1.11.12 to version request" and "Emulate -n checkout bug" ==> I tried his solution (settings in CVSNT) which failed at first. I checked it again and noticed that I enabled these parameters for CVSNT clients. So I tried to enable these parameters for non-CVSNT clients... which solved the problem. I get no errors anymore and tried to add, versionize and reload a little project which works as expected. thanks to you all for the help. Patrick "Tony Hoyle" <tony.hoyle at march-hare.com> schreef in bericht news:eavu08$7fl$1 at paris.nodomain.org... > patrick goovaerts wrote: >> hmmm, I'm using the latest version of IBM WebSphere Developer Studio >> which integrates RAD6.x into Eclipse (Eclipse JDK 3.0.2). > > It can't be the latest version - eclipse fixed that bug a long time ago. > I'd contact IBM about an upgrade. > >> I don't get this error when using CVSNT 1.11.3 but decided to install the >> latest version of CVSNT 2.5.03.2382 to start with... > > It's not a CVSNT problem. Certain old versions of eclipse had a bug where > they generated spurious error messages if they saw a repository without a > drive letter. This was fixed ages ago and should not occur any more. > > Tony