Eclipse Community Forums: Java Development Tools (JDT)

Home » Language IDEs » Java Development Tools (JDT) » Eclipse 3.0M5 and changes

Eclipse 3.0M5 and changes [message #122307]

Wed, 26 November 2003 08:52

Eclipse User

Originally posted by: a_jordanov.prosyst.bg

I was quite surprised when some plugins taht works fine on M4 doesn't work
on M5. Then I look for problem and I found Eclipse 3.0 porting guide. There
it was written that a new tag is included in plugin xml file - <?eclipse
version="3.0"?>
This change should allow the Eclipse runtime to reliaby recognize pre-3.0
plug-ins that have not been ported to 3.0, so that it can automatically
provide greater binary compatibility for such plug-ins.

I think that if I didn't specify this tag then my old plugins from
Eclipse2.1 or 3.0 M4 should work without any problem. Can somebody tell me
why they doesn't work then?
The log of workspace shows me that I had problem with IDocument.

Regards, Alex

Re: Eclipse 3.0M5 and changes [message #122743 is a reply to message #122307]

Thu, 27 November 2003 12:35

Eclipse User

From your description it looks like you are affected by a bug in the
backwards compatability support in M5. Please take a look at this defect
and try the patch.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=47463

Re: Eclipse 3.0M5 and changes [message #123102 is a reply to message #122307]

Sun, 30 November 2003 08:56

Eclipse User

"Eclipse Newsgroup" <a_jordanov@prosyst.bg> wrote in message
news:bq2b30$ado$1@eclipse.org...
> I was quite surprised when some plugins taht works fine on M4 doesn't work
> on M5. Then I look for problem and I found Eclipse 3.0 porting guide.
There
> it was written that a new tag is included in plugin xml file - <?eclipse
> version="3.0"?>
> This change should allow the Eclipse runtime to reliaby recognize pre-3.0
> plug-ins that have not been ported to 3.0, so that it can automatically
> provide greater binary compatibility for such plug-ins.
>
> I think that if I didn't specify this tag then my old plugins from
> Eclipse2.1 or 3.0 M4 should work without any problem. Can somebody tell me
> why they doesn't work then?

M5 does introduce a large number of breaking API changes in addition to
plugin dependency changes. Have your recoded you plugin to avoid the APIs
that were removed in M5? It took us several days to update all of our
products to work in M5.

-Eric Clayberg
Sr. Vice President of Product Development
Instantiations, Inc.
mailto:cpsws-support@instantiations.com
http://www.instantiations.com
http://www.instantiations.com/codepro/ws
http://www.swt-designer.com

Previous Topic:	importing packages
Next Topic:	Yet Another Desired Editing Feature

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Nov 09 10:48:50 EST 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter