Community
Participate
Working Groups
Team 2.0 provided a mechanism to allow our plugins to handle the delete and rename action. We need a similar mechanism for the refactor actions (copy, move, rename and delete) in the navigator for certain file types. The file types that are handled by our plugin require some special functionality when dealing with refactor actions. Currently, I am unable to override these actions. I am able to provide separate navigator view actions (using the extension org.eclipse.ui.popupMenus) but unable to override the default actions. Our IViewActionDelegates respond to selection changes in the navigator and enable or disable appropriately.
The changes for hooking move/rename/delete were essentially to support VCM providers, and was a change made only at the workspce level (in org.eclipse.core.resources). What you are asking for here does not fit into the mandate of that proposal. Is this support for VCM? Or is it some other use case where you are writing your own navigator-like view by extending the ResourceNavigator, and you simply need to handle these actions differently? If the latter, note that there has been some refactoring here recently which may make it easier. It would help to know more details about what you're trying to do.
Use Case: The following use case applies irrespective of whether project resources are under version control (team provider)or not. Our plugin has files that contain information about other supporting files. These supporting files exist only when the main file exists. When the main file is deleted the supporting files should also be deleted. The same scenario applies to copying, moving and renaming the main file. Currently Eclipse does not provide a PRE-DELETE event for deleted resources. We receive only a post change event. If the main file has been deleted then all information w.r.t the supporting files is lost. Possible Solutions: 1) Eclipse should notify all the resource change listeners by firing off PRE- events for all refactor operations (Copy, move, rename and delete) for the affected resources. 2) If the above is not possible then Eclipse should provide a mechanism to override the copy, move rename and delete actions in the navigator.
Moving to Core for consideration of solution 1.
*** Bug 37444 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 36943 ***