Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 330960

Summary: [ltk] refactoring is not triggered on project move
Product: [Eclipse Project] JDT Reporter: Kevin Tapperson <kevintap>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: markus.kell.r
Version: 3.6   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard: stalebug

Description Kevin Tapperson CLA 2010-11-23 14:04:40 EST
Build Identifier: M20100211-1343

The ltk refactoring extension is not triggered on a project move operation.  I have extended the org.eclipse.ltk.core.refactoring.moveParticipants extension point to participate in the project move operation, but it is not being called.

  <extension point="org.eclipse.ltk.core.refactoring.moveParticipants">
	  <moveParticipant
          id="my.test.moveProjectParticipant"
          name="%Move.Project"
	  	class="my.test.MoveProjectParticipant">
	  	<enablement>
			<with variable="element">
			  <instanceof value="org.eclipse.core.resources.IProject" />
		  	</with>
		</enablement>
	  </moveParticipant>
  </extension>

This seems like a bug to me, as I am able to extend the org.eclipse.ltk.core.refactoring.renameParticipants extension point to participate in the rename of a project, but I cannot get my move participant invoked when a project is moved.

Reproducible: Always

Steps to Reproduce:
1. create a plugin that uses the org.eclipse.ltk.core.refactoring.moveParticipants extension point as described in the details
2. move a project to a new location
3. the move participant is never called
Comment 1 John Arthorne CLA 2010-11-23 16:04:47 EST
LTK is actually part of JDT.
Comment 2 Markus Keller CLA 2010-11-25 11:55:35 EST
'Move project' is a bit special: Unlike all other resource move operations, there's no target IResource in this case.

Technically, it's not a resource move operation, so it can't be handled by the MoveResourcesProcessor and would have to be implemented as a separate refactoring.
Comment 3 Eclipse Genie CLA 2019-10-01 08:14:45 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.