Quick question about including/exposing dependencies for bundles running under felix.
As I understand it, there are predominantly 2 ways of exposing 3rd party libs for use in our bundle: 1) Include the 3rd party jar files in the bundle's /lib folder - which exposes all packages of the jar(s) to the code in the bundle. 2) Package the 3rd party jar/jars as an OSGi bundle, exporting the requisite packages in the bnd by way of the manifest. I seems like the first strategy encourages potential for future conflicts (if another bundle exports the same packages) but reduces the dependencies for the bundle, since its self-contained. The second strategy allows for reusability of code (all bundles that need 3rd party library X can get the dependencies for the same bundle) however this adds extra dependencies to the bundle deployment lifecycle (you may have ensure that when Bundle A is deployed, there is process in place to deploy 3rd party bundles X, Y and Z). - Thoughts around when to use one over the other? - Are there any other dangers to using either method I didn't outline above? - Any other options? Thanks -- David Gonzalez Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
