| Summary: | [Team API] move/copy semantics not preserved for VCM/targets (1G5RAC5) | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jeff McAffer <jeffmcaffer> |
| Component: | Team | Assignee: | Platform-VCM-Inbox <platform-vcm-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P5 | CC: | sven.koehler |
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Jeff McAffer
This won't be addressed in the 1.0 VCM API. We are looking at namespace support and requirements in the 2.0 API. Reopening I believe the move/delete hook gives repository providers the ability to preserve the semantics of a move. However, copy is still not covered. *** Bug 42962 has been marked as a duplicate of this bug. *** 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? 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. This bug has not been touched for 2 years. Closing as WONTFIX. Please reopen if you feel this is still an important issue. |