Community
Participate
Working Groups
1. add a file called foo.c to CVS 2. rename to Foo.c 3. Try to add Foo.c to version control -> displays error message Workaround: commit the deletion of foo.c first, then add Foo.c to version control. Øyvind
What CVS server version are you using. I tried this using CVS on Linux and it worked. If your using CVSNT then it's a server issue and there is little we can do.
>What CVS server version are you using. I tried this using CVS >on Linux and it worked. If your using CVSNT then it's a >server issue and there is little we can do. CVSNT Is there a list of known problems w/CVSNT and Eclipse? I work as a consultant and convincing my customer he should use CVS at all was hard enough. I know Linux CVS would have been a better choice. Øyvind
This is not an issue with Eclipse. This is an issue with CVSNT. Have you tried this using command line CVS? You will see that the operation fails in the same way. Keeping a list of Eclipe/CVSNT issues would be difficult because the list changes with every new build of CVSNT (builds seem to happen every month or two). However, we try to keep the FAQ up-to-date with known issues. I will add this to the FAQ. http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm- home/docs/online/cvs_features2.0/cvs-faq.html
>This is not an issue with Eclipse. This is an issue with CVSNT. CVSNT is a bit of an icky issue. In my case it was CVSNT or no CVS. We would have been told to use Visual Source Safe. I *MUCH* prefer CVSNT to VSS. >Have you tried this using command line CVS? No. This particular problem is more easily worked around in the GUI as I described. I suppose this bug-report should be categorized as known minor issue that will not be addressed by Eclipse. Øyvind
Actually, after some thought, I think that changing Team>Commit is wrong because this operation is meant to be as close to the behavior as "cvs commit" as possible. However, the operations in the sync view already perform special handling for certain cases. I believe it would be appropriate to modify the commit action in the sync view to perform outgoing deletions before adding new resources to version control. The update already does this for incoming changes. I have recategorized this as an enhancement. We will not have time to address it in 2.1.
>Actually, after some thought, I think that changing Team>Commit is wrong >because this operation is meant to be as close to the behavior as "cvs commit" >as possible. However, the operations in the sync view already perform special >handling for certain cases. I believe it would be appropriate to modify the >commit action in the sync view to perform outgoing deletions before adding new >resources to version control. The update already does this for incoming >changes. I have recategorized this as an enhancement. We will not have time to >address it in 2.1. Sounds great! Øyvind
This bug has not been touched for 2 years. Closing as WONTFIX. Please reopen if you feel this is still an important issue.
