| Re: [pdt-dev] PDT 1.1. - API updates following infra changes |
IMHO there should be no reason to delete files from version control just because somebody "started working on the API change", especially when there are other files which depend on them. It should be done in the end of the process, shouldn't it?
Seva
2008/6/25 Roy Ganor <roy@xxxxxxxx>:
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: pdt-dev-bounces@xxxxxxxxxxx [mailto:pdt-dev-bounces@xxxxxxxxxxx] 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
pdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pdt-dev
_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pdt-dev