Description Max Bureck 2016-03-14 14:51:03 EDT

I am currently trying migrate some views to be based on the e4 concepts, mainly to get rid of some platform dependencies to make these components more universally re-usable. These have to be used in new e4 based applications, in an old Eclipse 3 based application, and even outside of an RCP context. The only viable way to accomplish this seems to be to use the Eclipse 3 extension point "org.eclipse.ui.views" with the "e4view" element. Unfortunately it looks like this element (that was introduced with Eclipse Luna) is still not available in RAP 3.0.

The alternative to this extension point, the DIViewPart from e4 tools bundles, seem not to work due to hard Require-Bundle dependencies to workbench and SWT bundles. This solution is anyway hard use for applications targeting a platform version prior to Mars, since the list which versions of the update site is compatible with which version of the platform is not available anymore.

This makes it hard to write modern re-usable components and modernizing existing applications slowly.