Incompatibilities between Eclipse 4.3 and 4.4

Eclipse changed in incompatible ways between 4.3 and 4.4 in ways that affect plug-ins. The following entries describe the areas that changed and provide instructions for migrating 4.3 plug-ins to 4.4. Note that you only need to look here if you are experiencing problems running your 4.3 plug-in on 4.4.

See also the list of deprecated API removals for this release.

  1. Removed WorkspaceLock API
  2. Removed IncrementalProjectBuilder#getRule() API

1. Removed WorkspaceLock API

What is affected: Clients that directly reference WorkspaceLock API.

Description: The WorkspaceLock API allowed a special client (usually platform UI) to hook into the locking protocols used by the workspace implementation. This hook was used to mitigate deadlocks due to interaction with synchronous SWT events, and was never intended to be used by other clients. In the 3.0 release this API was deprecated in favor of a more general API provided by the org.eclipse.core.jobs bundle. Invoking this API has had no effect since the 3.0 release. The specific API being removed includes:

Action required: Clients that directly use API listed above should remove any references to it.

2. Removed IncrementalProjectBuilder#getRule() API

What is affected: Clients that directly call or implement IncrementalProjectBuilder#getRule() API.

Description: The IncrementalProjectBuilder#getRule() method returned a scheduling rule that was required for building the project by the builder. This method was intended to be used by the builder framework only. In the 3.6 release this method was deprecated in favor of a more general method IncrementalProjectBuilder#getRule(int, Map). The specific API being removed includes:

Action required: Clients that directly call API listed above should remove any references to it or replace with calls to IncrementalProjectBuilder#getRule(int, Map). Clients that implement API listed above should implement IncrementalProjectBuilder#getRule(int, Map) instead.