| RE: [pdt-dev] PDT 1.1. - API updates following infra changes |
|
Well, we are not “just removing”
it as we will provide a map between the old and the new API. Also DLTK’s API is not part of our
API since we are only a “client” of this project. The same way we are
heavily using WST as infrastructure level and this project’s API is not
our API. From: pdt-dev-bounces@xxxxxxxxxxx
[mailto:pdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of I'm not totally agree
with your point. 2008/6/26 Roy Ganor <roy@xxxxxxxx>: 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?
http://www.searchenginecaffe.com/2008/06/eclipse-ganymede-simultaneous-release.html From: pdt-dev-bounces@xxxxxxxxxxx
[mailto:pdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of
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 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:
Regards, _______________________
|