Osmorc Code

* Missing compiler output path will no longer throw NPE in Facet editor
* Osmorc is now asking if a manifest should be created instead of silently creating it.
* Added some more translations

OSMORC-9:
* Modules are now generated for framework instance libraries
* dependency synchronizer uses those generated modules
* Works most of the time. At some obscure situations some exceptions are thrown. Need to work on that a bit more.
Fixed some issues uncovered by IDEA's code inspections

Fixed ModuleDependencySynchronizerTest.

Fix for NullPointer that occurs on the first RunConfiguration in a project

OSMORC-9 : First steps to get this done.

* tried to make equinox running, but when it comes to eclipse, things tend to be non-working. changed hierarchy so it derives from abstractframeworkrunnner.

* Felix runner is now working, we can start bundles using felix!
* custom installation steps are now properly run before the osgi runtime is started
* renamed some methods in the frameworkrunner interface to better reflect their purpose
* created base class for runnners covering the common tasks for each runner
* modified test data

* Added support for completely automated Manifest generation to the bundle compiler (no more physical manifest file required, but of course supported if you wish to do so)
* It is now possible to specify bundle symbolic name, activator and version in the facet settings (only used for automated manifest generation).
* Manifest synchronizer now honours manifest path settings from the facet configuration, so it is now possible to have the manifest file anywhere in your project
* Facet configuration changes will now trigger resynchronization
* Added inspection reporting when a bundle activator is not set up in the manifest or facet configuration.
* Added some more translations
* Updated the test data

* It is now possible to specify the name and output folder of the built bundle. This is useful if you want to build your bundle using an external build tool (maven or ant) but still want to be able to launch the built bundle using a normal run configuration. It's also nice if you are using some hot deployer bundle which is watching some folder and deploys all new jar files within that folder.
* Added some (crappy) icons... I'm a coder, not an artist, Jim! Well, better than no icons at all.
* Updated test data a bit.