Re: [Dltk-dev] When drop eclipse 3.3 compatibility?

[Alex Panchenko <alex@xxxxxxxxx>]

Hi,

The only reason to drop 3.3 compatibility is the intent to use new 
platform features.
We can workaround some cases making a copy of the new methods/classes, 
but it is not always possible. Also some features require us to 
implement new interfaces, so there is no compatibility workaround.
The example I personally remember is ITextHoverExtension2, which is used 
to display quick-fixes in the same popup control as the error message. 
It looks pretty nice for JDT, but it is available only in Eclipse 3.4.

Regards,
Alex


Shelby Sanders wrote:
> All,
>
> We're still based on Eclipse 3.3, and currently don't have a near-term 
> plan for moving to 3.4 or later.
>
> We already have a local cache in place, so could just stop taking 
> updates.  However, that makes it much harder to collaborate and/or 
> contribute to HEAD.
>
> What is pushing for dropping 3.3 compatibility?  My feeling is that 
> it's been pretty easy to maintain so far.
>
> Thank You,
> Shelby Sanders
>
>
> On Nov 10, 2008, at 02:14AM, Alex Panchenko wrote:
>
> > Hi all,
> >
> > Are there any objections to drop eclipse 3.3 compatibility now and go
> > forward with eclipse 3.4?
> >
> > Thanks,
> > Alex
> >
> > _______________________________________________
> > dltk-dev mailing list
> > dltk-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/dltk-dev
>
> _______________________________________________
> dltk-dev mailing list
> dltk-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dltk-dev