Bug 7 - [Team API] move/copy semantics not preserved for VCM/targets (1G5RAC5)
Summary: [Team API] move/copy semantics not preserved for VCM/targets (1G5RAC5)
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P5 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-VCM-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 42962 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-10-10 21:34 EDT by Jeff McAffer CLA
Modified: 2005-05-06 17:18 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff McAffer CLA 2001-10-10 21:34:52 EDT 
The platform is able to notify people that a resource was moved using resource
change events (deltas).  It does not track copies.
In neither case is it easy for a VCM or target to retain the semantics of a move
or copy since by the time it is run, all it has it the current state (i.e., it can tell 
that a file was deleted and another added but not that this was a move).
This is unfortunate since the VCM/target sync code may well be able to do
optimizations if this information was available.

NOTES:

JM (12/10/2000 2:49:42 PM)
	This is related to 
		1G5RAC5: ITPCORE:WINNT - move/copy semantics not preserved for VCM/targets
	It is only relevant to address non-local move/copy if the above PR is addressed.  
	otherwise, there is nothing to do at release time since there is no local copy and all
	we can do is put/delete.

JM (4/15/2001 9:54:43 PM)
	There is nothing we can do about this now.  Moving to VCM for logging as a future
	issue.
Comment 1 Jean-Michel Lemieux CLA 2001-10-12 11:51:01 EDT 
This won't be addressed in the 1.0 VCM API. We are looking at namespace support 
and requirements in the 2.0 API.
Comment 2 Michael Valenta CLA 2002-09-08 15:37:40 EDT 
Reopening
Comment 3 Michael Valenta CLA 2002-09-08 15:39:12 EDT 
I believe the move/delete hook gives repository providers the ability to 
preserve the semantics of a move. However, copy is still not covered.
Comment 4 Michael Valenta CLA 2003-09-12 07:40:17 EDT 
*** Bug 42962 has been marked as a duplicate of this bug. ***
Comment 5 Sven Köhler CLA 2003-09-12 08:11:21 EDT 
Is this really only related to WinNT? I don't understand the problem yet:
- copying files works, copying folders doesn't
- copying folders to other projects with from different CVS repositories seems
to work without copying the CVS-Tag
- copying to unshared projects does work too

Under which circumstances is the CVS-Tag known to be copied from one project to
another?
Comment 6 Michael Valenta CLA 2003-09-12 09:14:24 EDT 
In response to the previous comment, no its not just NT. Also, the behavior 
you described is excatly what I would expect. The problem is that, to the CVS 
plugin, a copy to another project mapped to the same remote folder looks 
exactly like a Replace with Branch or Version. The other cases you mentioned 
are distinguishable and are hence handled properly.
Comment 7 Michael Valenta CLA 2005-05-06 17:18:53 EDT 
This bug has not been touched for 2 years. Closing as WONTFIX. Please reopen if 
you feel this is still an important issue.