Osmorc Code

OSMORC-27: Actually the real problem here doesn't seem to be editing a manifest outside of IDEA. That works perfectly. A Require-Bundle statement that makes a bundle require itself produces the exception shown in the bug report. Osmorc now doesn't try to add module dependencies from a module to itself even if the manifest requires it.

OSMORC-9:
* Rolled back part of the changes made to fix this bug.
* Now there is one module called "FrameworkInstance" that references all libraries of the curent framework instance
* Project modules now again reference the global framework instance libraries according to their bundle dependencies specified in their manifests.
* Creation of the module "FrameworkInstance" is now optional and deactivated by default (need to find the right default for the most common case)

* added possiblity to specify additional properties that are to be added to the manifest that is automagically generated by osmorc (e.g. properties for Spring Dynamic Modules or something else)

* added manifest filter to the bundle compiler to prevent compile failures due to manifest files in the compiler output path
* added more test data

* 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.