| Re: [platform-core-dev] Special notification rules need for move/ rename/delete hooks? |
When performing a move/rename/delete, ClearCase must
check out the parent directory(s) of the files/directories
being moved/renamed/deleted. Depending on a preference set
by the user, the parent directory(s) may be left in this new,
checked out state. I want this change picked up by Eclipse
so plugins can act appropriately (ex. the ClearCase plugin
would decorate the directory as checked out and enable the
"Check in" menu item).
Peter
> Subject: Re: [platform-core-dev] Special notification rules
> need for move/rename/delete
> hooks?
> To: platform-core-dev@xxxxxxxxxxx
> From: "John Arthorne" <John_Arthorne@xxxxxxx>
> Date: Wed, 13 Nov 2002 10:02:19 -0500
> Reply-To: platform-core-dev@xxxxxxxxxxx
>
>
> The move/delete hook is not permitted to modify anything in
> the workspace
> apart from the very carefully scoped task it is given. The
> only way to
> modify the resource tree from the move/delete hook is via the
> IResourceTree
> callback. That's why all the IMoveDelete hook API methods have the
> following paragraph:
>
> * The implementation of this method runs "below" the
> resources API
> and is
> * therefore very restricted in what resource API
> method it can call.
> The
> * list of useable methods includes most resource
> operations that
> read but
> * do not update the resource tree; resource operations
> that modify
> * resources and trigger deltas must not be called from
> within the
> dynamic
> * scope of the invocation of this method.
> * </p>
>
> Can you explain a bit more what you're trying to do, and why
> you need to
> modify parents of moved/deleted resources?
>
>
>
>
>
>
> "Hack, Peter" <PHack@xxxxxxxxxxxx>
> To: "'platform-core-dev@xxxxxxxxxxx'"
>
> Sent by: <platform-core-dev@xxxxxxxxxxx>platform-core-dev-admin@
> cc: eclipse.org
> Subject: [platform-core-dev] Special notification rules need for move/rename/delete hooks?
>
> 11/07/2002 01:55 PM
>
> Please respond to platform-core-dev
>
> If a move/rename/delete hook (from a Team provider) modifies a
> directory/file that's not explicitly passed in to the hook
> (ex. the parent
> directory of the file being moved/renamed/deleted), what are the
> appropriate rules and mechanism to use to provide notification of That
> side-effect change? I don't know if this has to be dealt
> with as a special
> case
>
>
>
>
>
>
> --__--__--
>
> _______________________________________________
> platform-core-dev mailing list
> platform-core-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-core-dev
>
>
> End of platform-core-dev Digest
>