Hi Michael, Thanks for your reply. Kindly see few of my comments, below.
On Mon, Sep 21, 2009 at 9:16 PM, Michael Glavassevich <[email protected]> wrote: > Does the Eclipse team have a plan for when they might reach API stability? I don't think so, Eclipse WTP team has any concrete plans at the moment, when they might reach API stability for PsychoPath. Here is a link to the proposed API changes with PsychoPath: http://dev.eclipse.org/mhonarc/lists/wtp-wst-dev/msg00321.html This is just a proposal at the moment, with no time frame as such, when these changes would get implemented, and in which WTP release it would be part of. I have conveyed to the PsychoPath team, that it would be good, if they do API changes, after PsychoPath processor reaches 100% compliance (or near to that) to the spec, with a corresponding WTP milestone release from Eclipse. But 96% compliance if also good, with WTP 3.2M1 release (but that's with JDK 5) :) > Incompatible changes to an API are a pain for consumers and would prefer if > we didn't start introducing code to cope with incompatible changes to the > PsychoPath API. I agree. > I do think the instability is okay at the moment because we have not had a > release yet and once we do it would be a "developer preview" where we warn > our users that things can and will change in the future. We could just > change our code to align with the updates to the API. That's nice, and I agree as well. > However, once XML > Schema 1.1 is included in a Xerces release from the main trunk I would hope > that the PsychoPath API is stable and that the Eclipse team isn't changing > it in the future in ways which could potentially break users. I hope so. I'll share these thoughts with the PsychoPath team, so they could be careful about this. I think, it would be good (as is a general practice with successful projects) if PsychoPath can deprecate older public APIs, instead of dropping any APIs suddenly. > Would also be nice if the API signatures stay compatible with Java 1.3 (i.e. > don't have visible dependencies on classes / interfaces in JDK 1.4+) so that > it's possible for us to make a final JDK 1.3 PsychoPath jar around the time > of the first "production" release, but also allow users to obtain newer > versions from eclipse.org which may have internal dependencies on Java 5+. I'll convey this to PsychoPath team. But porting a future 100% compliant PsychoPath code base in entirety to JDK 1.3, would be pretty challenging. PsychoPath does have plans, to port it's releases in future to JDK 1.4 (but not 1.3). Let's see how all this goes in future. I'll work with PsychoPath team, and would try to have minimal impact on Xerces code, and it's users. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
