XtextRenameResourceParticipant is unnecessarily loaded for rename actions

XtextRenameResourceParticipant.initialize(..) returns true by default, without checking if the renamed element is relevant for this participant. That causes unnecessary appearances of a refactoring dialog within our Eclipse-based application.

The participant should at least consider the if checks from the addElement(..) method for its return value.
So instead of:

@Override
	protected boolean initialize(Object element) {
		addElement(element, getArguments());
		return true;
	}

It should be something like:

@Override
  	protected boolean initialize(Object element) {
          if (arguments instanceof RenameArguments && element instanceof IResource) {
              addElement(element, getArguments());
              return true;
          }
          return false; 
       }

Locate XtextRenameResourceParticipant and inspect initialize(..) alongside addElement(..), especially the checks involving RenameArguments and IResource. Adjust the initialization decision so irrelevant elements are rejected, then verify that rename actions for those elements no longer open the refactoring dialog while relevant resource renames still do.