In the last chapter, we looked at the way Eclipse 4 RCP applications are built. We'll now look at how to migrate an existing solution based on Eclipse 3.x APIs to Eclipse 4.x, and the pros and cons of migrating to the new infrastructure.
In this chapter, we shall:
Migrate an existing Eclipse 3.x view to an Eclipse 4.x view using the e4view extension
Replace deprecated Action classes with generic classes
Create code to show a toolbar, view menu, and pop-up menu
Create an e4xmi fragment to migrate to Eclipse 4.x models
Define commands, handlers, toolbars, view menus, and pop-up menus in the model
Do forward selection between Eclipse 3.x views and Eclipse 4.x parts