On 22/07/07, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
On Sunday 22 July 2007 10:50, Stuart McCulloch wrote: > Now, how is BND going to determine if > > Import-Package: packageB > > or > > Import-Package: packageC > > that's why BND takes a classpath *and* a set of instructions Well, yes and no. BND takes instructions, but it should also protest when the instructions don't match the set up.
agreed - there are checks and error messages for various mismatches, but of course this can always be improved. specific cases should be recorded as JIRA issues against the maven-bundle-plugin with details on how to recreate.
1) consistency - this is the expected behaviour compared to other BND > plugins, and what I would expect to see My argument is that BND is fed too much information. If that is the case for the other use-cases of it, then that are separate bugs.
we should probably go through the use-cases - I can think of a few where having a complete classpath is necessary. imho too much info is better than not enough, as extraneous info can be ignored but missing info is hard to replace.
2) flexibility - I may want to take a package from a provided dependency > and include it in my bundle (I can't see any reason why this should be > disallowed - and changing the dependency to compiled could have unforseen > side-effects) We obviously need to discuss this face to face.
yep :) need to brainstorm this on the whiteboard... There IS a difference between packages in an included jar and a package in
an imported jar.
indeed, and I believe this can be captured in the BND directives, but there may be an opportunity to simplify this... 1. Packages that are used by the packages in the included jar MUST be
imported if not found in the elsewhere in the bundle. 2. Packages that are used by Imported-Packages are not to be resolved in this bundle.
Cheers
-- Niclas Hedhman, Software Developer I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug
-- Cheers, Stuart
