Eclipse e3 to e4 migration/adaption(preferred) - recommendations

Question

What I got

I got a nearly finished e3 application, but need the dependency injection feature from e4, therefore I moved to Kepler.

Now in e4, the e3 plugins are working, if I run my application as an e3 App. But if I change to Application.e4xmi the system fails. (somehow expected this)

Problems

How can I move my e3 plugins to e4 so my perspectives and views are working (I got plenty of em! And I cannot remove them - I need them to be extended if an plugin gets added!) also Menu contributions, Handlers/Commands need to work (nothing in my fragment.e4xmi gets added to the gui)

What I did till now

I changed my api to e4 so I no longer use IWorkbench or PlatformUI nor ViewPart interfaces (still some way to go, only did this in one plugin for testing purposes)

Transformed my plugin.xml (e3 code) to an e4 fragment.e4xmi (but found out (link to stackoverflow) that contributing views/perspectives is broken in e4.)

I added the fragment.e4xmi as extension in my plugin.xml and removed everything else (e3-style)

Resources

1. Stackoverflow
2. Lars Vogel
3. Jonas Helming

Edit/Updates

1. Bug 376486 - Eclipse 4 IDE not extendable via fragments or processors - so how do you extend your e4 Application - if its not working via fragments or processors?
2. to raise the possibility of an solution i split up the problem and described a part here

Answer 1

solving this required creation of an e3 Application in an e4 workspace. then create POJO views and use the Wrapper Class to enable DI.

detailed solution for building it up can be found here