> Thanks for the reply and excellent clarification. Instead of OSGi bundle > just think JAR. I have the structure that you suggested except that I > did not use an assembly because I could not see how to create a JAR that > only contained the contents of I and P and not all of their dependencies.
Not sure to understand yours needs, but did you look at the maven-bundle-plugin from Felix community ? http://cwiki.apache.org/FELIX/maven-bundle-plugin-bnd.html It has been designed to control OSGi packaging (include or not dependencies, generate and validate OSGi Manifest properties, ...) in a maven system. I'm widly using it to build OSGi applications (up to 150 bundles), with separated API, implementations and consumer services ... Damien Lecan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
