Searched refs:rename (Results 1 – 14 of 14) sorted by relevance
24 import org.eclipse.jdt.internal.corext.refactoring.rename.RenameTypeProcessor;
27 import org.eclipse.jdt.internal.corext.refactoring.rename.RenamePackageProcessor;
29 import org.eclipse.jdt.internal.corext.refactoring.rename.RenameFieldProcessor;
60 import org.eclipse.jdt.internal.corext.refactoring.rename.RenameCompilationUnitProcessor;61 import org.eclipse.jdt.internal.corext.refactoring.rename.RenameTypeProcessor;
55 import org.eclipse.jdt.internal.corext.refactoring.rename.RenameCompilationUnitProcessor;56 import org.eclipse.jdt.internal.corext.refactoring.rename.RenameTypeProcessor;
42 import org.eclipse.jdt.internal.corext.refactoring.rename.RenameTypeProcessor;
61 import org.eclipse.jdt.internal.corext.refactoring.rename.RenameFieldProcessor;
358 public boolean rename(INode node) { in rename() method
38 AIDL_Java_Conflict=%1$s is in the way of %2$s, remove it or rename of one the files.
193 if (!mRulesEngine.rename(node)) { in addContextMenuActions()
161 public boolean rename(INode node) { in rename() method in ClientRulesEngine
840 config.rename(name); in initializeName()
824 mManager.rename(mDescription, newName); in click()
1143 void rename(ConfigurationDescription description, String newName) { in rename() method in RenderPreviewManager