"Steven E. Harris" <[EMAIL PROTECTED]> writes: > Would this mean creating a Maven project in my own source tree and > pointing it at the tracker code, requesting the appropriate packages > for export?
I figured it out. It's explained in the "Real-World Example" section of the "Bundle Plugin for Maven" documentation.¹ What's not obvious is whether the plugin automatically includes any dependencies of the exported "borrowed" package. That is, when I write <Export-Package>org.osgi.util.tracker[,...]</Export-Package> in my pom.xml file, I see that all of the org.osgi.util.tracker package gets copied into my bundle.² But what if this package makes use of other packages for implementation that would normally be specified in a Private-Package declaration? Will the Bundle Plugin know to include these in my bundle? I must say this whole approach of borrowing parts of other bundles makes me uneasy. Isn't it possible that these individual class files may rely on other resources being present in the bundle? Is a package name really sufficient to capture the cohesive set of resources? Footnotes: ¹ http://cwiki.apache.org/FELIX/bundle-plugin-for-maven-bnd.html ² That is, so long as the dependency on the org.osgi.compendium artifact does not have "provided" scope. -- Steven E. Harris
