| Migration from E3 + compat to Pure E4 application [message #1706505] |
Thu, 27 August 2015 08:32  |
Eclipse User |
|
|
|
Hallo,
I have an Eclipse 3.x application project that was migrated into Eclipse 4.x by using the compatibility layer.
Now I am investigating the migration to a pure Eclipse 4 application, and I will need a suggestion:
To investigate which classes to fix I will remove all the 3.x dependencies from the manifest of my project.
As example, I know that org.eclipse.core.runtime is part of eclipse 3.x and it must be removed to have a pure E4 application.
Now, my questions are:
- Is there a list of the dependencies to remove in order to have a pure e4 application?
- Do you think this is a good way to investigate the migration from e3.x to e4.x ?
Thanks in advance
Kind Regards,
Patrik
|
|
|
|
| Re: Migration from E3 + compat to Pure E4 application [message #1706513 is a reply to message #1706507] |
Thu, 27 August 2015 09:04  |
| Eclipse User |
|
|
|
Hi,
Simon Scholz and I are currently writing a migration tutorial. The resulting code can be found here: https://github.com/fipro78/e4-cookbook-migration-guide
In short, everything that starts with org.eclipse.ui is bad when talking about plain e4. 
I agree with Tom that it depends on your application whether it is a good idea to migrate or not. Typically I would always suggest to migrate, but I also faced issues where it is not possible to migrate easily. Especially when third-party plug-ins come into play it might get a mess if they are not migrated. In such a case you are forced to have the compatibility layer in play, and this might lead to strange situations.
Regarding the EditorPart, well, maybe it depends to the EditorPart, but we also migrated one in our migration tutorial, and sure it is some more work, but also not too bad.
|
|
|
Powered by
FUDForum. Page generated in 0.08478 seconds
Home