Bug 206456 - Copy operation overwrites CVS metadata
Summary: Copy operation overwrites CVS metadata
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.3.1   Edit
Hardware: PC Windows XP
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-16 09:03 EDT by Bryan Mason CLA
Modified: 2019-09-06 16:16 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bryan Mason CLA 2007-10-16 09:03:14 EDT
Simply copying a folder (using drag and drop or copy/paste from within the package explorer view) from one project with CVS folders to another project that is connected to CVS will alter version control information.  This is unexpected; I expect this problem when done using a native OS copy command, but not when done through Eclipse.  I think it is reasonable to expect that Eclipse, being aware of
version control schemes, can exclude CVS/SVN/etc version information metadata
folders where appropriate.

Without this patch, it becomes the Eclipse user's responsibility to make sure that underlying version control system files are properly maintained.  The default package explorer filters hides the CVS folders (unless you know and delete them manually from outside of Eclipse), so it is very easy to overlook that Eclipse does not do this automatically.  Eclipse does a great job integrating CVS behind the scenes currently, but this pitfall makes it very hard to keep CVS metadata
accurate.

See reference to this bug, filed March 2004 that point to this same problem.... https://bugs.eclipse.org/bugs/show_bug.cgi?id=54415
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:16:23 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.