This guide covers migrating Eclipse 4.16 plug-ins to Eclipse 4.17.
One of the goals of Eclipse 4.17 was to move Eclipse forward while remaining compatible with previous versions to the greatest extent possible. That is, plug-ins written against the Eclipse 4.16 APIs should continue to work in 4.17 in spite of any API changes.
The key kinds of compatibility are API contract compatibility and binary compatibility. API contract compatibility means that valid use of 4.16 APIs remains valid for 4.17, so there is no need to revisit working code. Binary compatibility means that the API method signatures, etc. did not change in ways that would cause existing compiled ("binary") code to no longer link and run with the new 4.17 libraries.
While every effort was made to avoid breakage, there are a few areas of incompatibility or new APIs that should be adopted by clients. This document describes those areas and provides instructions for migrating 4.16 plug-ins to 4.17.