Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The rename refactoring has several processors that subclass <a href="http://grepcode.com/file/repository.grepcode.com/java/eclipse.org/3.6.1/org.eclipse.ltk.core/refactoring/3.5.100/org/eclipse/ltk/core/refactoring/participants/RenameProcessor.java#RenameProcessor" rel="noreferrer"><code>org.eclipse.ltk.core.refactoring.participants.RenameProcessor</code></a> and are responsible for renaming different elements. For example, there is a processor for renaming Java projects <a href="http://grepcode.com/file/repository.grepcode.com/java/eclipse.org/3.6.1/org.eclipse.jdt/ui/3.6.1/org/eclipse/jdt/internal/corext/refactoring/rename/RenameJavaProjectProcessor.java#RenameJavaProjectProcessor" rel="noreferrer"><code>org.eclipse.jdt.internal.corext.refactoring.rename.RenameJavaProjectProcessor</code></a>. A refactoring participant can participate in the condition checking and change creation of a refactoring processor. For example, to check some conditions during a rename refactoring, you should subclass <a href="http://grepcode.com/file/repository.grepcode.com/java/eclipse.org/3.6.1/org.eclipse.ltk.core/refactoring/3.5.100/org/eclipse/ltk/core/refactoring/participants/RenameParticipant.java#RenameParticipant" rel="noreferrer"><code>org.eclipse.ltk.core.refactoring.participants.RenameParticipant</code></a>, override the method <a href="http://grepcode.com/file/repository.grepcode.com/java/eclipse.org/3.6.1/org.eclipse.ltk.core/refactoring/3.5.100/org/eclipse/ltk/core/refactoring/participants/RefactoringParticipant.java#RefactoringParticipant.checkConditions%28org.eclipse.core.runtime.IProgressMonitor,org.eclipse.ltk.core.refactoring.participants.CheckConditionsContext%29" rel="noreferrer"><code>org.eclipse.ltk.core.refactoring.participants.RefactoringParticipant.checkConditions(IProgressMonitor, CheckConditionsContext)</code></a> and register the participant via the extension point <code>org.eclipse.ltk.core.refactoring.renameParticipants</code>. The participant <a href="http://grepcode.com/file/repository.grepcode.com/java/eclipse.org/3.6.1/org.eclipse.jdt/ui/3.6.1/org/eclipse/jdt/internal/corext/refactoring/nls/NLSAccessorFieldRenameParticipant.java#NLSAccessorFieldRenameParticipant" rel="noreferrer"><code>org.eclipse.jdt.internal.corext.refactoring.nls.NLSAccessorFieldRenameParticipant</code></a> gives you a good example of how to participate in a rename refactoring.</p> <p>When you declare your extension of the <code>org.eclipse.ltk.core.refactoring.renameParticipants</code> extension point, you should specify the element you'd like your participant to get notified about. For example, see how the following use of the <code>org.eclipse.ltk.core.refactoring.renameParticipants</code> extension point in <a href="http://grepcode.com/file/repository.grepcode.com/java/eclipse.org/3.6.1/org.eclipse.jdt/ui/3.6.1/plugin.xml/?v=source" rel="noreferrer"><code>org.eclipse.jdt.ui/plugin.xml</code></a> involves the participant in renaming fields.</p> <pre><code>&lt;extension point="org.eclipse.ltk.core.refactoring.renameParticipants"&gt; &lt;renameParticipant class="org.eclipse.jdt.internal.corext.refactoring.nls.NLSAccessorFieldRenameParticipant" id="org.eclipse.jdt.ui.NLSFieldRenameParticipant" name="%Refactoring.NLSFieldRenameParticipant"&gt; &lt;enablement&gt; &lt;with variable="affectedNatures"&gt; &lt;iterate operator="or"&gt; &lt;equals value="org.eclipse.jdt.core.javanature"/&gt; &lt;/iterate&gt; &lt;/with&gt; &lt;with variable="element"&gt; &lt;instanceof value="org.eclipse.jdt.core.IField"/&gt; &lt;/with&gt; &lt;/enablement&gt; &lt;/renameParticipant&gt; &lt;/extension&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload