Deprecated API can be marked for deletion without requiring a major version increment. See the policy for the details. This section describes API removals that occurred in past releases, and upcoming removals in future releases.
API Changes prior to CDT 10.0 / 2020-09.
Prior to CDT 10 release API changes were published as part of the New and Noteworthy entries for that release. From CDT 10 forward breaking API changes are included in this document.
API Changes in CDT 10.0.
Planned Removals after June 2022
See Bug 562494.
A review of the previously exported API of CDT was performed. A lot of what was previously marked as public API has
now been marked as internal. This means the API has either had x-internal or x-friends
added to the Export-Package declarations.
The following bundles have had all their packages exported as internal See Bug 561389:
The following bundles had additional changes made to be able to mark packages as internal:
Where possible bundles have had their Activators removed. Some of these activators were API and are no longer available. See Bug 561635 for workarounds where items that used to be in Activators are still needed, such as logging and plug-ids.
The following Activators that were API have been removed.
The NewClassCreationWizardPage has some API breaking changes due to how some protected fields, especially
ALL_FIELDS was used. While this breaks binary
compatibility, no code changes should be needed in extenders, just compiling against the new version. See Bug 510789 and Bug 561770.
The items below can be removed after the given date or on the next major release, whichever is sooner. The details and discussion on the removal happens in the Bugzilla associated with the entry below. See the policy for the details.
The following binary parser classes have replacements, mostly due to these versions not supporting 64-bit variants of the binary files. The new 64-bit parsers support both 32 and 64 bit files.
See Bug 562495.