[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-vcm-dev] Team + Refactoring
|
I recently integrated our Stellation plugin with the resource delta
mechanism, to transparently update the local Stellation branch image for
resource moves and renames. This allows us to maintain resource history
across such changes.
Originally, I tried the MoveDeleteHook mechanism, but found that it was a
poor choice for the reasons Michael Valenta mentioned.
Note that the ResourceDelta information will contain two elements for each
resource move:
a MOVED_FROM and a MOVED_TO. It was also useful to have the ResourceVisitor
build a list of resource updates, so I could update the Stellation image in
a single batch operation
(YMMV, of course).
Regards,
Jim
At 12:11 PM 6/18/2002 -0400, David Corbin wrote:
Clemm, Geoff wrote:
Could you explain a bit more why you believe the resource delta
mechanism is relevant to "move"?
Because if I move a resource, I don't want to lose the history of that
resource. Perforce supports this. We need to support it in the perforce
plugin-in.
Semantically, a move
is orthogonal to delta information (i.e. a move registers
a resource at a new location, and therefore is a namespace
operation, which does not affect the resource content).
I understand your point about being orthogonal to delta information, but
it's not orthogonal to source code control.
_________________________________________________
Jim Wright
Stellation Project (Advanced Programming Tools Group)
IBM T.J. Watson Research Center
