Hi Peter, On 12/5/06, Peter Kriens <[EMAIL PROTECTED]> wrote:
PN> - is maven capable of using the resulting bundle as a dependency for PN> the next bundle (I think not) The bnd plugin does not use the bundle classpath so the results are also valid for normal maven dependencies, they are normal jars with flattened classpaths (unless you hardcode it yourself).
I'm mostly thinking of the fact that a bundle is an assembly of jars, even if it is packed itself as a jar. This may lead to confusion since you have a jar artifact (the bundle) as an outcome that may not be working as a regular jar when it is referenced as a compile time dependency from another project, since the class files may not be directly under the root. I think that might give problems later on when people start gettng comfortable with bundles and use more of the possibilities in the OSGi spec for bundles. Then we actually will have to figure out what that bundle actually is exporting, not what is packaged as class files under the root.
PN> - is the bnd plugin capable to figuring out the imports and exports PN> from only ingoing .jar files, meaning that more or less all bundles PN> look like library bundles? (I guess that is there or would be I think so, but I am not a 100% sure I understand the question ...
I think much of this is covered by your reply to Emil. /peter
