Hi, I see. The problem is that you added the optional element.
If you have scope=provided, these bundles don't add to the transitive dependencies of oak-core and as such this suffices it. The optional element is AFAICT only required to remove scope=compile dependencies from the transitive dependency space. Regards Felix Am 09.10.2012 um 11:39 schrieb Chetan Mehrotra: > Probably I was not clear before. So would try to explain it through an > example. Have a look at oak-core [1] > > 1. Non OSGi Usecase - Any other Maven module which depends on > oak-core should not require the osgi related jars at runtime. To > support that case the org.osgi.core dependency has been marked as > optional. Its fine to have the osgi metadata in the manifest file but > osgi related jar should not be part of runtime classpath > > 2. OSGi Usecase - In osgi env the packages related to osgi core should > be required and not marked as optional > > Now if I mark the org.osgi.core dependency as optional (#1) the > maven-bundle-plugin would mark packages from it as optional which > conflicts with #2. So I am looking for a way to achieve both #1 and #2 > > Chetan Mehrotra > > [1] https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/pom.xml > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
