Re: [cdt-dev] API changes related to obsolete class PluginVersionIdentif

[Chris Recoskie <recoskie@xxxxxxxxxx>]

I don't think anyone is really using it. The versioning/updating code in MBS is pretty busted. I'd be surprised if anyone was relying on it as a result.

I would support changing it. PluginVersionIdentifier has been deprecated for quite a long time now.

I had already put on the agenda for the Summit to discuss versioning and updating (both for MBS levels and toolchain level), so this probably dovetails into that. I haven't put together anything significant in the way of thoughts of how to go about doing it better. Mainly I just know that I have the requirements that a) you can update to a new version of MBS, and b) you should be able to version and update/convert your tools/toolchains/etc. independently of the MBS revision without breaking your users' existing projects.

===========================
Chris Recoskie
Team Lead, IBM CDT and RDT
IBM Toronto

Andrew Gvozdev ---07/02/2010 01:52:47 PM---There is a proposed patch in bug 318581<https://bugs.eclipse.org/bugs/show_bug.cgi?id=318581>to repl

From:	Andrew Gvozdev <angvoz.dev@xxxxxxxxx>
To:	"CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date:	07/02/2010 01:52 PM
Subject:	[cdt-dev] API changes related to obsolete class PluginVersionIdentifier in managedbuilder plugin
Sent by:	cdt-dev-bounces@xxxxxxxxxxx

---

There is a proposed patch in bug 318581 to replace deprecated PluginVersionIdentifier from org.eclipse.core.runtime with org.osgi.framework.Version as PluginVersionIdentifier's JavaDoc suggests.
However, there are a few classes in MBS which are using it as API:
- IBuildObject
- IManagedIsToolChainSupported
- ManagedBuildManager
- UpdateManagedProjectManager
- IsGnuCygwinToolChainSupported

We could try to preserve the API by deprecating interfaces/methods using the obsoleted class and introduce new clean interface in 8.0. But in this case I don't think many ISVs are affected and the transition is pretty straightforward. I'd rather replace it and be done with that. There are only 2 MBS plugins affected, org.eclipse.cdt.managedbuilder.core and org.eclipse.cdt.managedbuilder.gnu.ui.

Please, let me know if there is a good reason to conserve that API in MBS.

Thanks,
Andrew_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev