[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse-dev] External editor plug-ins broken in M5
|
actually, that plugin was very nice (i used to use it all the time), but
AFAIK it hasn't worked properly in any of the 3.0 builds...
-alvin
On Wed, 2003-11-26 at 14:35, John Wiegand wrote:
>
>
> Bob,
>
> Just to amplify on John Arthorne's comments:
>
> We invest considerable effort ensuring that plug-ins continue to work in
> new releases of the platform; however, we are not perfect. Your plug-in
> broke in M5 because of a bug in our 2.x compatability support. A patch to
> fix this defect in M5 has been created and is available (see
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=47463).
>
> If you find another case where your plugin is affected by API breakage
> please take the time to report the problem; we will either
>
> - Enhance our backwards compatibility support,
> - Back out, or provide an alternate change, or
> - Update the porting guide (see
> http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.eclipse.platform.doc.isv/porting/eclipse_3_0_porting_guide.html)
>
> Let me reiterate that the intent is for Eclipse 3.0 to be compatible with
> Eclipse 2.x to the greatest extent possible. We need your experiences, and
> the experiences of all plug-in writers to help us achieve these
> compatability goals.
>
> John Wiegand
>
>
>
> John Arthorne
> <John_Arthorne@ca. To: eclipse-dev@xxxxxxxxxxx
> ibm.com> cc:
> Sent by: Subject: Re: [eclipse-dev] External editor plug-ins broken in M5
> eclipse-dev-admin@
> eclipse.org
>
>
> 11/26/2003 07:15
> AM
> Please respond to
> eclipse-dev
>
>
>
>
>
>
>
> Bob, we implemented a compatibility layer for M5 that should have prevented
> errors like this by automatically mutating the set of required plug-ins for
> "legacy" 2.1-based plug-ins . Unfortunately there was a typo that
> prevented it from working in the case of jface.text. This wasn't discovered
> until M5 was out the door. It has been marked as a critical defect and a
> patch is available in the bug report:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=47463
>
> Please enter bug reports if we drop shoes on you in the future <g>.
>
> John.
>
> eclipse-dev-admin@xxxxxxxxxxx wrote on 11/26/2003 05:56:26 AM:
>
> > Thanks, Kai,
> >
> > I have actually looked at that stuff before. I assume it's in there
> > somewhere you moved the package to some plug-in that my plug-in doesn't
> > depend on, so the class can't be loaded. I've been waiting for the shoe
> to
> > drop.
> >
> > But I have to ask, why would I want to make my plugin run in M5 when the
> > M5-compatible version probably won't run in M6, and so on?
> >
> > Granted you have to shuffle things around to make the RCP, but how about
> > letting us know when you're going to _stop_ dropping shoes?
> >
> > Bob Foster
> >
> >
> > > Bob,
> > > M5 is a major step towards a Rich Client Platform. Please have a look
> at
> > > "What's new and noteworthy"
> > >
> > http://download.eclipse.org/downloads/drops/S-3.
> > 0M5-200311211210/eclipse-news-M5.html
> > >
> > > especially the section about the Rich Client Platform
> > >
> > http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-ui-
> > home/rcp-proposal/rich_client_platform_facilities.html
> > >
> > > There you will find general information and also the steps how to
> migrate
> > > your plug-ins to run on M5.
> > > Kai
> > >
> > >
> > >
> > >
> > >
> > > java.lang.NoClassDefFoundError:
> > > org/eclipse/jface/text/BadLocationException
> > >
> > > Thanks. Good job.
> > >
> > > Bob Foster
>
>
> _______________________________________________
> eclipse-dev mailing list
> eclipse-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> http://dev.eclipse.org/mailman/listinfo/eclipse-dev
