gurkerl83 edited a comment on pull request #78: URL: https://github.com/apache/jclouds/pull/78#issuecomment-650395849
The integration of OSGi into JClouds is really only superficial. Not OSGi near component models like Declarative Services or Blueprint were chosen as CDI but simply Guice. Don't be frightened if OSGi Metadata declarations are present in all bundle POMs. These aspects are still relevant. Here we should switch to the use of the BND Maven plugin, but it's best to outsource the OSGi rules contained in the pom to bnd files. Especially good is already the use of the Service Provider Interface (SPI) as a plugin framework, which is not OSGi specific and has been supported by Java for a long time. The OSGi package contained in the core module and its classes, especially MetadataBundleListener through the implementation of the interface BundleListener react when a bundle with an entry in /META-INF/services/ is loaded into the OSGi runtime environment. In short, you can move the bundle to a new module and the function will be preserved without problems. At this point you have to integrate e.g. Aries SPI-fly bundle into the OSGi runtime environment so that the bundle listener reacts to this kind of events. Then there is only the part included in ScriptBuilder module, which I will have a look at tomorrow. Over the weekend I will describe the procedure, which components are affected and how a solution could look like as a JIRA ticket. I'm also willing to help out with the JClouds aspects handed over to Karaf. I have opened an issue in this project to learn more about the future development of the project. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
