Over the weekend due to some confusion about Java version dependencies and where/if the errors should be picked up we identified that some of CDTs bundles did not have API Tooling enabled. This is an oversight that makes it difficult to identify when API gets broken by simple changes.
For CDT 10 M3 and beyond API Tooling will be enabled on all bundles to make it easier to understand how we may have changed API for our consumers. Note that for experimental and preview bundles (as marked in their name) this does not change the stability of those APIs.
See Bug 566334 for more details and to add your comments.
> On 24 Aug 2020, at 22:42, Jonah Graham <[hidden email]> wrote:
> ... some of CDTs bundles did not have API Tooling enabled. ...
I discovered that this is part of Eclipse Plugin Development Environment (PDE), but a quick explanation would help to understand what this means.
API Tools is the part of PDE that verifies that you have maintained your API contract as compared to your previous releases. e.g. it will give you an error to tell you to increment the minor version if you introduce a new method in a public API class. If you remove a method it will tell you to increment the major version number.