RE: [platform-vcm-dev] Team + Refactoring (cont.)

["Clemm, Geoff" <gclemm@xxxxxxxxxxxx>]

This is a significant bug.  A move/rename is not a modification
to the file being moved, it is a modification to the directory/folder
that originally contained the file, and a modification to the
directory/folder that will contain the file.

So MOVE(/a/b, /c/d) should result in an IFileModification to
/a and an IFileModification to /b, not to /a/b or to /c/d.

Similarly, a DELETE(/a/b) should result in an IFileModification
to /a, not to /a/b.

On the other hand, a COPY(/a/b, /c/d) should result in an
IFileModification to /c/d.

Cheers,
Geoff

-----Original Message-----
From: David Corbin [mailto:dcorbin@xxxxxxxx]
Sent: Thursday, June 20, 2002 6:44 PM
To: platform-vcm-dev@xxxxxxxxxxx
Subject: [platform-vcm-dev] Team + Refactoring (cont.)


When a Java file is renamed, I'm getting a call to 
IFileModification.validateEdit with a null context.  This is problematic 
for us.  We really need to know that it is being moved before it is 
being edited.  

I'm not (personally) familiary with IFileModification, but is there any 
way for us get the move first before the edit attempt, or for the 
validateEdit to provide context that tells us this is being called as 
apart of a rename/move?

Thanks
David Corbin

_______________________________________________
platform-vcm-dev mailing list
platform-vcm-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev