Bug 125148 Cleanup of Team content provider
I made a change in the SynchronizationContentProvider that allows the AbstractRefactoringSynchronizationContentProvider to be cleaned up a bit *I will attach a patch). The change involves how a listener gets registered (i.e. it is now done byu the superclass) so there is no change in behavior associated with this fix. It is strickly code hygien.
org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/ui/refactoring/model/AbstractRefactoringSynchronizationContentProvider.java
import org.eclipse.core.resources.IProject;
import org.eclipse.core.resources.IResource;
import org.eclipse.core.resources.IStorage;
import org.eclipse.ltk.core.refactoring.RefactoringCore;
import org.eclipse.ltk.core.refactoring.RefactoringDescriptor;
import org.eclipse.ltk.core.refactoring.RefactoringDescriptorProxy;
import org.eclipse.ltk.core.refactoring.history.IRefactoringHistoryService;
import org.eclipse.ltk.core.refactoring.history.RefactoringHistory;
import org.eclipse.ltk.internal.core.refactoring.history.RefactoringHistoryImplementation;
import org.eclipse.ltk.internal.core.refactoring.history.RefactoringHistoryService;
import org.eclipse.ltk.internal.ui.refactoring.RefactoringUIMessages;
import org.eclipse.ltk.internal.ui.refactoring.RefactoringUIPlugin;
import org.eclipse.ui.IMemento;
import org.eclipse.ui.navigator.IExtensionStateModel;
/**
 * Partial implementation of a refactoring-aware synchronization content
 * provider.
 * <p>
 * Note: this class is intended to be extended by clients who need refactoring
 * support in a synchronization content provider.
 * </p>
 * <p>
 * Note: This API is considered experimental and may change in the near future.
 * </p>
 * 
 * @see org.eclipse.team.ui.mapping.SynchronizationContentProvider
 * 
 * @since 3.2
 */
public abstract class AbstractRefactoringSynchronizationContentProvider extends SynchronizationContentProvider {