Incompatibilities between Eclipse 3.5 and 3.6

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

  1. SDK ships 2 org.junit plug-ins (versions 3.8.2 and 4.8.1)
  2. Source incompatibility for subclasses of AbstractTemplatesPage

1. SDK ships 2 org.junit plug-ins (versions 3.8.2 and 4.8.1)

What is affected: Clients that require the org.junit and don't include 4.x in their version bounds

Description: The SDK now ships 2 org.junit plug-ins (versions 3.8.2 and 4.8.1). Clients that want to run JUnit Plug-in Tests with a Java 5 or later VM and that require org.junit with a version bound that does not include 4.x need to update their version bound to include 4.x (e.g. change their Require-Bundle: header to org.junit;bundle-version="3.8.2"). If they don't update their bounds, both versions of org.junit are resolved at run time, which leads to errors when test classes are loaded.

For complete details on the steps required to transition to using JUnit4 or to continue using JUnit3, please see:
http://wiki.eclipse.org/Eclipse/Testing/JUnit4_Changes.

Action required: Clients that require org.junit should make sure they include 4.x in their required version bounds.

2. Source incompatibility for subclasses of AbstractTemplatesPage

What is affected: Subclasses of org.eclipse.ui.texteditor.templates.AbstractTemplatesPage.

Description: In order to provide new API we had to make two methods public. While this does not break binary compatibility it breaks source compatibility.

Action required: Change the visibility of getSelectedTemplates() and getTemplateStore() to public.