> Could you give me an example of how you separate your API and > implementation. Do you use separate poms, or within the same pom ? If > within the same pom how do you check that only the API is used by other > poms ? If in separate poms how do you build the bundle ?
There are 2 things in your questions : - how am I deploying my OSGi applications - how am I building my OSGi bundles The second question depends on the 1st one. With OSGi, you can choose where you want to deploy java classes. I can reduce an OSGi application to 3 components : - service consumers (SC) - service descriptions (API) - service producers (SP) Dependencies : SC -> API <- SP Many packaging solutions can found : all together or each component in its own bundle. Ok, packaging SC + API together is a bad idea, but packaging API + SP can be done. This last solution is a problem only when you can have several SP for the same API. So, basicaly, I have : Parent pom +- SC (depends on API with scope "provided") +-API +-SP (depends on API, can embed API if API scope is "compile") If you want 3 bundles, don't embed API in SP If you want 2 bundles, embed API in SP (just a pom configuration) Is it what you want ? Damien Lecan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
