Community
Participate
Working Groups
Setting: CVS server 1.12.3 on AIX, Eclipse 2.1.1 on Windows XP with the cvs.jar patch (2003-10-20) from bug 45138. A file has been checked out by Developers A and B; Developer A deletes the file and commits (B has made no changes to the file). Developer B does "Team -> Synchronize with Repository..." in Eclipse Java Perspective on the directory containing the file. Effect: the file is not shown as deleted (no error message). Developer B does "Team -> Synchronize with Repository..." in Eclipse Java Perspective on the file itself. Effect: Eclipse Popup "Internal error" and an exception trace in .metadata/.log (see attachment). Going back to CVS 1.11.10 on the server fixed the problem.
Created attachment 7213 [details] Eclipse exception trace of "Team -> Synchronize ..." on file deleted in CVS by a team mate
I haven't conformed this particulr failure yet but there does seem to be some major differences in 1.12.x that are causing problems (at least in the automated tests). Will investigate.
Given that 1.12 is a feature release of CVS, we will deal with any incompatibilities nearer the end of 3.0.
*** Bug 51509 has been marked as a duplicate of this bug. ***
*** Bug 51276 has been marked as a duplicate of this bug. ***
Created attachment 10390 [details] A patch to the CVS core plugin to handle file deletion in CVS 1.12.x This is a small patch to the 2.1.3 release of the cvs core plugin for Eclipse. It handles the new message format that CVS version 1.12.x uses to inform of files that have been moved to the attic and should therefore be removed from the user's local copy. It should be backwards compatible with CVS version 1.11.x, but this has not been tested.
Created attachment 10391 [details] Updated CVS core plugin with patch applied for Eclipse 2.1.3 Patched 2.1.3 CVS core plugin
Thanks for the patch. It has been applied to 3.0 and does not impact 1.11.x compatibility. Leaving open to allow people to find the patch to 2.1.3 (and as a reminder to add it to the FAQ).
FAQ updated. LEaving open to make patches available
FAQ has been updated to point at the patches. No further action is planned.