Eclipse Community Forums: Eclipse 4 » Migrating 3.x RCP Applications on Eclipse 4 SDK

Home » Eclipse Projects » Eclipse 4 » Migrating 3.x RCP Applications on Eclipse 4 SDK(does backward compatibility layers supports to run my 3.x RCP on e4 without any changes?)

Show: Today's Messages :: Show Polls :: Message Navigator

Migrating 3.x RCP Applications on Eclipse 4 SDK [message #653056]

Tue, 08 February 2011 09:51

Praveen

Messages: 86
Registered: July 2009

Member

I would like to migrate my existing 3.x RCP application to Eclipse 4.1 SDK. However, when I run the application in e4, the launch fails with unavailability of Application Model file (Application.e4xmi). Do I really need to create the Application Model file for my 3.x RCP application ?

I was under impression that backward compatibility layer should take care of launching 3.x RCP applications. Are there any best practices or rules required for the migration ?

PS: The main intention of migration is to understand the e4 architecture so that we can contribute back to e4 both in terms of reporting broken functionality and contribute patches to make e4 more stable.

Report message to a moderator

Re: Migrating 3.x RCP Applications on Eclipse 4 SDK [message #653061 is a reply to message #653056]

Tue, 08 February 2011 10:04

Thomas Schindl

Messages: 6651
Registered: July 2009

Senior Member

Hi,

You need to have a minimal e4xmi like shown here:
http://thomaskratz.blogspot.com/2010/11/uhh-we-have-color-ru nning-legacy-app-on.html

And a description here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=317912

But we should definately document this on the wiki.

Tom

Am 08.02.11 10:51, schrieb Praveen:
> I would like to migrate my existing 3.x RCP application to Eclipse 4.1
> SDK. However, when I run the application in e4, the launch fails with
> unavailability of Application Model file (Application.e4xmi). Do I
> really need to create the Application Model file for my 3.x RCP
> application ?
>
> I was under impression that backward compatibility layer should take
> care of launching 3.x RCP applications. Are there any best practices or
> rules required for the migration ?
>
> PS: The main intention of migration is to understand the e4 architecture
> so that we can contribute back to e4 both in terms of reporting broken
> functionality and contribute patches to make e4 more stable.

Report message to a moderator

Previous Topic:	Resetting a .xwt resource DataContext
Next Topic:	Changes with e4 4.1 m5

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 02:06:55 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter