Since 1.0.x branch contains all this
information (and can be used as a reference) and since the old model is
malfunctioning rather than deprecated (as explained in the previous email) and
since the malfunctioning model takes lots of lots lines of code there is no
reason to keep it alive. Moreover I don't want that people use it incorrectly,
they should search for a reference in the JDT or DLTK platforms. As my previous
email says it is a necessary move rather than desirable.
About the versioning matter, I do agree with
Nick, we should call this version 2.0. Guy (the project leader) is going to
decide how to handle this from here.
Thank you for the feedbacks!
BTW – have you seen this incredible demo?
Can you please share some draft document (e.g. a wiki page) to explains main
points of the issue before the first session?
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.
step following our infra changes is to change Eclipse PDT 1.1 API.
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
following extension points will be replaced with our new API:
- org.eclipse.php.core. includePathVariables
Team Leader, R&D
Zend Technologies Ltd.
pdt-dev mailing list