Re: [pdt-dev] PDT 1.1. - API updates following infra changes
I've just discovered almost all the classes from org.eclipse.php.internal.core.phpModel
package have been suddenly removed from CVS, which caused basic stuff inside org.eclipse.php.ui
not to compile.
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?
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.
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
Team Leader, R&D
Zend Technologies Ltd.
pdt-dev mailing list