On 12/6/06, Aaron Siri <[EMAIL PROTECTED]> wrote:
I think Emil (correct me if I'm wrong) and I would both like to see only packages from bundle dependencies added to Import-Package, not stuff from embedded plain old jars (which should instead be added to the classpath.) The new plugin's behavior for this is nice, as long as it only looks at bundle dependencies and not jar dependencies. I think Emil is then saying that if both a bundle and a plain old jar provide a package then don't put it on Import-Package (i.e. let it resolve to the plain old jar via the classpath.) The embedded plain old jars should override bundles (maybe OSGi spec already dictates this.)
This is exactly what I want. If the plugin did this then I would be fine. All my posts so far can be summarized with this: Bundle B depends on A. Then: A is bundle => generate Import-Package. A is jar => embed and add to Bundle-Classpath. Apply recursively. [snip]
P.S. I want to thank Richard and Peter for putting up with all of my questions/complaints. I'm learning a lot in this newsgroup.
Yes, likewise. Thanks for your patience and help in figuring this all out! -EE
