Peter Kriens wrote:
RSH> No, it won't. Classes on the bundle class path will be considered part
RSH> of the content of the bundle and BND will not generate imports for
RSH> packages that are part of the content of the bundle.
Unless you export them of course ...
If you export them, BND won't generate imports for them, it will
generate exports for them, correct? We are talking about the metadata of
the bundle itself, not of other bundles.
-> richard
Kind regards,
Peter Kriens
RSH> On Jan 25, 2007, at 4:27 PM, Emil Eifrém wrote:
On 1/25/07, Richard S. Hall <[EMAIL PROTECTED]> wrote:
This instruction would be used to match the specified Maven
dependencies
for embedding. Any matching dependency would have its JAR file
embedded
onto the resulting bundle JAR file and it would be appended to the
Bundle-ClassPath header after ".".
Hey, thanks guys for coming back to this issue. The proposal is a good
step forward. One question tho. If I use a class that is provided by a
jar file on Bundle-Classpath... won't the plugin still generate an
Import-Package statement for the package of that class? If it does, it
is my understanding that an osgi runtime will reject our bundle since
it won't find a matching Export-Package anywhere.
RSH> No, it won't. Classes on the bundle class path will be considered part
RSH> of the content of the bundle and BND will not generate imports for
RSH> packages that are part of the content of the bundle.
->> richard
