Incompatibilities between Eclipse 4.19 and 4.20

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

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

  1. Update to Servlet 4
  2. Update to Jetty 10

1. Update to Servlet 4

What is affected: Clients that use Servlet APIs coming with Eclipse Platform.


Eclipse has updated to ship Servlet API to version 4 from previous version 3.

Bundle javax.servlet is renamed to jakarta.servlet-api to reflect the Servlet API being developed by JakartaEE project now.
Version 4.0 still keeps the javax.servlet package names as change to jakarta.servlet package names is not yet adopted by Eclipse.

Action required:

  1. Adjust build scripts, target platform and etc. to use the new bundle symbolic name.
  2. Implement and adjust to new Servlet 4.0 APIs

2. Jetty updated to version 10.x

What is affected: Clients that use embedded Jetty server coming with Eclipse Platform.


Eclipse has updated embedded Jetty server to version 10.x.

Bundle org.eclipse.jetty.continuation is removed from Jetty 10 and thus no longer shipped with Eclipse Platform. It is superseeded by the official Servlet 3.0 APIs.

Action required:

  1. Remove dependency on org.eclipse.jetty.continuation bundle from target platform, build scripts and other places referencing it
  2. Port any usage of API from that bundle to official Servlet APIs