Reply
Contributor
BillS
Posts: 39
Registered: 09-04-2008
0
Accepted Solution

Eclipse 3.5 vs Eclipse 3.4 for plugin work

Just checking to see if anyone's run into issues with Eclipse 3.5.X for SDK work, as it looks like the Execution Monitor example used it (org.eclipse.ui.views behaves differently in 3.4 than it does in the example provided) and I'd like to upgrade so I'm in sync with the version I use for non-iTest stuff but don't really want to break things.

 

 

Community Leader
PaulD
Posts: 1,214
Registered: 09-02-2008
0

Re: Eclipse 3.5 vs Eclipse 3.4 for plugin work

Note that the upcoming version of iTest will be built on top of Eclipse 3.5.  I'm not aware of any problems in building iTest 3.4 plugins using Eclipse 3.5 -- although you might need to be careful that you are not creating any dependences on Eclipse 3.5 plugins.  (Eclipse likes to add plugin dependencies that refer to the latest version of certain plugins and that could potentially cause issues when that plugin will end up in an RCP (iTest) that is built on the previous version.)

 

When creating your new plugin project, if you want it to work on iTest 3.4, make sure that you target Eclipse 3.4 in the first page of the new plugin project wizard.  

Contributor
BillS
Posts: 39
Registered: 09-04-2008
0

Re: Eclipse 3.5 vs Eclipse 3.4 for plugin work

Thanks Paul - I'm familiar with the general Eclipse pitfalls, just wanted to make sure..

Community Leader
AdamB
Posts: 721
Registered: 09-01-2008
0

Re: Eclipse 3.5 vs Eclipse 3.4 for plugin work

iTest 4.0 is based on Eclipse 3.5.2, so when adding the Eclipse SDK plugins, you will want to make sure to get the right versions.


Does this post answer your question? Click the "Accept as solution" button.

Was this post helpful? Click the yellow "Kudos!" button.