(1) move .classpath in his eclipse project out of the way and cvs update (you might have to exit eclipse to do this)
(2) manually add .classpath to his CVS/Entries file (at the project top level) - this can be dangerous if you do not know CVS well
jeff
[EMAIL PROTECTED] wrote:
One of our guys here was working on a project in Eclipse while I was mavenizing the dependencies and running "maven eclipse" to update .classpath. When I was done, I asked him to update his project so that he could get the new .classpath and be on his way. Unfortunately, CVS came back with an error saying that .classpath already exists. He had already made some code changes, so we couldn't just checkout the whole thing. Has anybody encountered this? Any workarounds?
Yoway Buorn Software Engineer Imagery Systems Engineering
GENERAL DYNAMICS Advanced Information Systems
"Make me a fire and I'm warm for a night. Set me on fire and I'm warm for the rest of my life." -- Ancient Didactical Saying
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- jeff bonevich mailto: [EMAIL PROTECTED]
"Any sufficiently advanced technology is indistinguishable from magic." Arthur C. Clarke
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." Rich Cook
"All programmers are playwrights and all computers are lousy actors." Unknown
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
