Re: [cdt-dev] [cross-project-issues-dev] No CDT update in 2022-12 M2 & M

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

On Wed, 26 Oct 2022 at 12:06, Liviu Ionescu <ilg@xxxxxxxxxx> wrote:

> On 26 Oct 2022, at 18:47, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
>
> ... I am happy to work with any downstream consumers if you find that you have build breakages due to CDT API changes - https://github.com/eclipse-cdt/cdt/blob/main/NewAndNoteworthy/CHANGELOG-API.md#api-changes-in-cdt-110 .

I don't know if this is relevant, but Eclipse Embed CDT uses some old APIs.

How can we check if these changes have any negative impact?

For embed-cdt, I have that open in my workspace, so for now nothing to worry about AFAICT. For other projects try building against pre-release of CDT, either from the https://download.eclipse.org/releases/2022-12 repo or from CDT directly like https://github.com/eclipse-cdt/cdt/blob/main/Downloads.md#development-builds. 

While this is a major version change and we will be breaking APIs, the intention in CDT is not to remove APIs that are known to be in use in the community. There are so many things which are technically API, but there are no known users of the API so keeping them going forward is just extra complication. That said there can be changes which are source code compatible that won't be binary compatible (such as a method the changes return type). So I try to keep an eye on that too.

As you may have seen, there are other breaking API changes coming in Eclipse Platform that is more likely to affect projects on the release train than what CDT is intending to change, such as the change that Alexander posted earlier today - https://www.eclipse.org/lists/cross-project-issues-dev/msg19420.html

HTH

Jonah

 

Liviu

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev