Community
Participate
Working Groups
Unfortunately I checked in a directory which was not supposed to be checked in. So I tried the following: 1. move directory to another location 2. commit the fact that the directory no more exists 3. move directory back to old location 4. add directory to .cvsignore The last step doesn't work, though. Right-clicking on the directory in the package explorer doesn't allow to choose option "add to .cvsignore", and even creating a .cvsignore by hand and add the directory name to it doesn't help.
The workaround is to log into the server and remove the folder *** This bug has been marked as a duplicate of 79869 ***
Well, you called your solution a "workaround", and I would probably agree with that. On the other hand, I don't think it's a good idea to play around with the CVS files manually. The feature request made in 79869 is related to my "bug", of course, but it's not the same imho. It would be nice to have such a "general exclusion" feature, but CVS support should also work fine without this feature, shouldn't it?
In general, is is a bad idea to play around with CVS files manually. However, CVS has particulary poor handling of empty folders. If you accidentially created a foolder on the server and it contains no file history that anyone cares about, than it is OK to remove it. One must still take great care when doing this. As for having Eclipse behave as the command line client does, we could do this but then most Eclipse CVS users would be very dissappointed. One of the Eclipse CVS selling points is that it isolates the user from the nitty gritty of CVS, the most important selling feature being the synchronize view. This feature comes at a cost especially considering that it is built on top of CVS which was never intended to provide this capability. The cost is that Eclipse CVS needs to keep track of all server directories, including those that are empty. This causes the Eclipse CVS client behavior to differ from the command line client behavior in this respect. This bug has been marked as a duplicate of bug 79869 because I felt that this was the best way to handle it, given all the factors. If you feel strongly that this is a separate issue, feel free to reopen it.
