Re: [cdt-dev] Is an API Baseline update to Neon.3 ok?

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

Hi Liviu, 

None of the Deprecated code in CDT will be removed anytime soon. Not before CDT 10.0, which is a long way off (in fact there is no major version bump planned in CDT.)

The Platform has a similar long retention policy on Deprecated code. The minimum is they keep the code for 2 years after announcing intention to delete the code. And deprecating code in itself ia not an intention to delete the code, but rather an indication that there is a newer/better way to do something. 

https://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy

HTH 

Jonah 

On 17 May 2017 06:58, "Liviu Ionescu" <ilg@xxxxxxxxxx> wrote:

> On 16 May 2017, at 13:10, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
>

> ... Are you asking if shipping the GNU ARM Eclipse plug-ins with a minimum

> version of CDT of 9.2.1 is OK?

yes

> I certainly think so.

great!

> It sounds like that will ease your testing
> burden because that will mean only Neon.3 and Oxygen versions are
> supported/verified. While I think the CDT 8.x vs CDT 9.x issues have
> now been resolved for you, not having to worry about supporting CDT
> 8.x seems like a positive too.

I just updated my development environment to Eclipse Neon.3, and reconfigured the project build to 9.2.1 API Baseline, with Java 1.8.

The good news is that the builds passed, both the maven repositories build, and the internal Eclipse build, for debug.

The bad news is that I have 190 deprecation warnings... :-(


looks like I'll have some very boring next few days...


regards,

Liviu

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev