Robert F. Beeger - 15 Jun 08 23:25 This was the first idea I had: Generate global libraries for all framework instance libraries and then generate dependencies on those libraries as packages are imported and bundles are required. It had some drawbacks such as that you couldn't search for classes of framework instance bundles that were not required or imported by any bundle in the active project. The second idea also doesn't work to my satisfaction: Wrap the libraries into generated modules. Now Osmorc generates modules for all libraries of the used framework instance. That works OK, but still has some problems. The third approach I'll try will solve this issue as well: Generate modules and module libraries for each bundle of the used framework instance. We'll see

Robert F. Beeger - 22 Jun 08 02:34 In framework instance creation dialog there is now an option to not create global libraries for framework instance bundles. In the case that no global libraries are generated, dependency resolution won't work when the bundle that would satisfy a dependency is one of the framework instance bundles. In this case there is no endpoint for a matching module dependency in IDEA. This option may be useful for projects, for which the manifest files are generated during the build process, since here there are no OSGi dependencies Osmorc can analyze and resolve. When the manifest files are edited during development time, the global libraries should be generated. Only with them dependencies on framework instance bundles can be resolved. Global libraries are the best way to cope with the fact that framework instances may be installed at different locations on different computers.