If you're *breaking* API, I think you need to upversion to PDT 2.0. If you're *adding* or *changing* API it but it's binary compatible, you can stay at 1.1.
http://wiki.eclipse.org/Version_Numbering And if you have to upversion anyway, wouldn't this be a great time to refactor org.eclipse.php to org.eclipse.pdt? :) Nick 2008/6/25 Roy Ganor <[EMAIL PROTECTED]>: > Consulting with other committers, it is important to have a discussion about > the new API. > > Two sessions will be held (scheduled later) about the API change, the first > one to collect feedbacks and the second to present the final API. > > > > ________________________________ > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Roy Ganor > Sent: Wednesday, June 25, 2008 1:24 PM > To: PDT Developers > Subject: [pdt-dev] PDT 1.1. - API updates following infra changes > > > > Hello there, > > > > Unavoidable step following our infra changes is to change Eclipse PDT 1.1 > API. > > Yes, it is a necessary step rather than a desirable one, we first thought > that we could write adapters to the old model but the ROI is low. In order > to step forward we must "slice" the cake and make a few changes. A detailed > document about our new API should be delivered shortly after we finish the > migration work. > > > > The following extension points will be replaced with our new API: > > org.eclipse.php.core. includePathVariables > org.eclipse.php.core.modelFilter > org.eclipse.php.core.phpBuilderExtensions > org.eclipse.php.core.phpModelExtensions > org.eclipse.php.core.workspaceModelListener > > > > Regards, > > _______________________ > Roy Ganor > Team Leader, R&D > tel. +972-3-7539637 > mob. +972-52-3290-754 > Zend Technologies Ltd. > > > > > > _______________________________________________ > pdt-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/pdt-dev > > _______________________________________________ pdt-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/pdt-dev
