Community
Participate
Working Groups
Make sure that when we remove sync info for a resource that we are deleting the resource (and all its children?) if there is no other info. NOTES: DJH (5/3/01 8:35:02 AM) Should we be deleting children automatically? Consider the following: - have project /proj - have phantoms /proj/a, /proj/a/b, /proj/a/c (note: all have sync info) - set the sync info for /proj/a to be null - /proj/a is a phantom and is no longer synchronizing so we should delete it - but its children still have sync info - should we go by the assumption that if the parent is no longer synchronizing, then the children aren't either? - can you synchronize subtrees? - I think targets can! DJH (5/4/01 7:14:26 PM) We will not allow the synchronization of subtrees. This is just too expensive w.r.t. the deletions and garbage collection. Currently VCM forces the user to synchronize at the project level. With targets we will add to the API that if a user wants to synchronize a subtree, then they must put sync info on the parents of the tree.
Created attachment 2627 [details] Test case for checking expected behaviour Adds a test case to ISynchronizerTest that removes a resource, sets its sync info to null and ensures the phantom does not exist any more. Tests when the removed resource is a file and a folder containing a file. Please verify and release.
Test case released into HEAD.
