Eclipse 2.1 and 3.0 plugin development

[Gregg Bolinger]

I understand that plugins targeted for eclipse 2.1.1 won't work on Eclipse 3.0 unless recompiled for 3.0. I was wondering if there was something special or specific about 3.0 compared to 2.1 that changes the way plugins are developed or if it is just the framework that the plugins are compiled with that make the difference. If there are differences, does your book cover anything about plugins for 3.0 since 3.0 hasn't been released as a final yet?
Thanks.

[Lasse Koskela]

I'd say the correct statement would be may not work -- I got my playground plugin working by importing the project into Eclipse 3.0... Then again, the plugin didn't use SWT classes (maybe that could be a factor?).

[Dave Vick]

In going through the plugin tutorial, I couldn't get the read-me plug-in to show up in the IDE. The read-me plug-in is for 2.1 (from the plugin.xml file) and I'm running version 3.0. The IDE doesn't even recognize it as a plugin - I wonder if it is something as simple as the version number in the xml file - hmm, gotta try that.

...
Nope that wasn't it
If there was a way to get the source then I wonder if you could just open it in 3.0 and compile it there?

[Gregg Bolinger]

Originally posted by Dave Vick:
If there was a way to get the source then I wonder if you could just open it in 3.0 and compile it there?

I think that is probably what has to be done from what I have read.

[Lasse Koskela]

The Eclipse 3.0 Porting Guide might give you a picture of whether a particular plugin needs tweaking in order to migrate from 2.x to 3.0.