The primary goal of eclim is to bring Eclipse functionality to the Vim editor. The initial goal was to provide Eclipse’s java functionality in vim, but support for various other languages (c/c++, php, python, ruby, css, html, xml, etc.) have been added and several more are planned.
1. The first scenario is for those for which vim is their primary editing interface. In this scenario you run a headless instance of eclipse which all vim instances can then communicate with to provide the various eclipse features.
2. The second scenario is for those who prefer using vim as their main interface, but frequently end up jumping back to eclipse for any features not provided by eclim. In this case you can run the eclim server inside of the eclipse gui and then interact with it via external vim instances just like the first scenario.
3. The last scenario is for those who wish to use the eclipse interface full time, but want to use gvim as an embedded eclipse editor. Just like the previous use case, the eclim server is run inside of the eclipse gui and the embedded gvim will interact with it just like external vim instances would.
Compile them both eclim and eclipse due to eclim needs eclipse 3.5.x is really hard and has so many MBs of dependencies.
I forgot to add the uri, http://