NEW DATE! Bugzilla will undergo maintenance 2024-03-28 18h00 CET. Bugzilla will be placed in read-only mode at that time.

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 17944 - Sync info on source of project move lost
Summary: Sync info on source of project move lost
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.0.1   Edit
Assignee: DJ Houghton CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 17548 21662 (view as bug list)
Depends on:
Blocks: 17548
  Show dependency tree
 
Reported: 2002-05-27 12:44 EDT by Michael Valenta CLA
Modified: 2002-08-01 11:24 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Valenta CLA 2002-05-27 12:44:31 EDT
It appears that the sync info associated with a project is lost if the project 
is moved. Because of this, we cannot keep the target provider mapping (DAV or 
FTP) when a project is moved.
Comment 1 DJ Houghton CLA 2002-05-27 14:11:40 EDT
Ensure that the sync info for the source of a move is left behind and a 
phantom is created.

Check to see if this is also the case when a project is the source.

Investigate for 2.0.
Comment 2 DJ Houghton CLA 2002-05-27 14:17:27 EDT
Note that the spec vaguely says that when you delete a non-project resource 
then the sync info is retained. Does/should that imply that project sync info 
is not retained when the project is deleted? Investigate.

Also consider the sync info files on disk. If the project doesn't exist 
anymore then where do the sync info files live since there is no meta data 
area for the project?
Comment 3 DJ Houghton CLA 2002-05-27 14:48:53 EDT
*** Bug 17548 has been marked as a duplicate of this bug. ***
Comment 4 Michael Valenta CLA 2002-05-28 09:39:34 EDT
Perhaps it would be acceptable in the move case to move the sync info with the 
project. For project deletions, the sync info could disappear. This is the 
behavior that we want for the target providers. I can't see why other 
synchronizer users wouldn't want this. 
Comment 5 Michael Valenta CLA 2002-07-17 15:04:19 EDT
*** Bug 21662 has been marked as a duplicate of this bug. ***
Comment 6 DJ Houghton CLA 2002-07-22 15:08:11 EDT
Consider for 2.0.1.

Sync info for a resource move should not be retained unless the resources are 
projects. Note that we don't want to retain sync info or create phantoms for 
the source of the move, only move the info to the destination.

See Workspace.copyTree and Workspace.createResource for potential location of 
fix. May require changes in move/delete hook helper class 
ResourceTree.movedProjectSubtree.
Comment 7 DJ Houghton CLA 2002-08-01 11:24:02 EDT
Fixed and released into both HEAD and 2.0.1 stream.
Closing.