Re: [eclipse-dev] External editor plug-ins broken in M5

["Bob Foster" <bob@xxxxxxxxxxxx>]

John,

Please forgive my belaboring the point, but doesn't this bug that slipped by
in M5 suggest there is something missing in the test cycle, namely trying to
run some third-party plug-ins? I know I am not alone having this problem; I
have been in contact with another plug-in writer who reported they have had
to change the plugin.xml in virtually all their plug-ins. Newsgroup reports
suggest that most third-party editor plug-ins were broken by M5.

I hate to bring up the past, I do see an increased awareness of such issues
now, but I had problems in the 2.1 cycle where api was broken and all the
eclipse.org plug-ins were simply changed to accomodate it (or didn't use the
api to begin with). Therefore, all the tests passed.

Bob

----- Original Message ----- 
From: "John Arthorne" <John_Arthorne@xxxxxxxxxx>
To: <eclipse-dev@xxxxxxxxxxx>
Sent: Wednesday, November 26, 2003 9:15 AM
Subject: Re: [eclipse-dev] External editor plug-ins broken in M5


> 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
>