LTK Core API changes

This document lists the API changes that occurred between R3.3 and R3.4 and how to migrate from the R3.3 API to the R3.4 API.

LTK Core Refactoring - Breaking API changes from R3.3 to R3.4
None

LTK Core Refactoring - Non-breaking API changes from R3.3 to R3.4

Added 'Rename resource refactoring' (Pushed down from JDT).

- `RenameResourceDescriptor`: refactoring descriptor to configure and create a refactoring
- `RenameResourceChange`: Change to rename a resource
- `ResourceChange`: Abstract base class for resource changes

All in package `org.eclipse.ltk.core.refactoring.resource`.

Added 'Move resources refactoring' (`org.eclipse.ltk.core.refactoring.resource`).

- `MoveResourcesDescriptor`: refactoring descriptor to configure and create a refactoring
- `MoveResourceChange`: Change to move a resource

Added 'Delete resources refactoring' (`org.eclipse.ltk.core.refactoring.resource`).

- `DeleteResourcesDescriptor`: refactoring descriptor to configure and create a refactoring
- `DeleteResourceChange`: Change to delete a resource

`ProcessorBasedRefactoring (org.eclipse.ltk.core.refactoring.participants`) can now be instantiated (was abstract before).

- the default implementation of `getProcessor()` now returns the processor passed in `ProcessorBasedRefactoring(RefactoringProcessor)` or by (new API) `setProcessor(...)`
- `ProcessorBasedRefactoring(RefactoringProcessor)` made public (was protected)
- `setProcessor` added as new API

Added `PerformRefactoringHistoryOperation.createRefactoring(RefactoringDescriptor, RefactoringStatus, IProgressMonitor)`) as replacement for `createRefactoring(RefactoringDescriptor, RefactoringStatus)` (deprecated).

Added API `ParticipantExtensionPoint (org.eclipse.ltk.core.refactoring.participants)` to be used to manage contributions of participants.

API changes from 3.2 to 3.3 can be found here.