Community
Participate
Working Groups
I'm working with maven, which creates a folder named 'target'. Somehow, Eclipse decided ths is part of the CVS. The folder is not in CVS, and is in .cvsignore. (I've used emacs & cvs cli to make certain that's the case). I've deleted the folder from within and outside eclipse, refreshed, created it from within and outside of eclipse, and always, when I do 'synchronize with repository', eclipse changes CVS/Entries and thereafter considers this folder as part of CVS. I've changed permissions for CVS/Entries, and eclipse creates it new. I've changed ownership to root, and then eclipse complains: Problems reported while synchronizing CVS Workspace. 0 of 1 resources were synchronized. An error occurred synchronizing xxxx: Errors saving CVS synchronization information to disk. Please fix the problems listed below and then update the affected resources from the CVS repository. Errors saving CVS synchronization information to disk. Please fix the problems listed below and then update the affected resources from the CVS repository. Could not write to read-only file: xxx/CVS/Entries. Could not write to read-only file: xxx/CVS/Entries. 1. The action of openning the synchronization perspective should not write CVS/Entries. 2. Eclipse should refresh correctly. If I edit CVS/Entries manually, removing a folder (or file), then after refresh, Eclipse should no longer consider them as part of the repository, even if I create them again.
Does the target folder exist in the repository? You can find out by expanding the project in the Repositories view.
the directory does not exist in the cvs repository
Is this reproducable for you? If so could you provide a set of steps that reproduce the problem (preferably starting from a new project since that's how I would have to try and reproduce it). Another thing you coudl ry is this. After the target folder is created and appears in Eclipse, open up the Properties dialog on the folder from the context menu. In the CVS tab, there should be a Disconnect button. Try that and see if it fixes the problem.
1. the target directory *was* in the cvs (was looking in the wrong directory, sorry) 2. to reproduce, do the following a. delete manually some entry from CVS/Entries b. refresh in eclipse c. verify that CVS/Entries is still modified d. do 'team->synchronize with repository' --> CVS/Entries is written by eclipse (or maybe the cvs process). but this should happen only on updating.
*** This bug has been marked as a duplicate of 79869 ***
