On 2 February 2010 23:25, Richard S. Hall <[email protected]> wrote:
> On 2/2/10 10:07, Craig Ching wrote: > >> Oh man, this is so classic and so me :-P The problem was I had >> Bundle-Classpath instead of Bundle-ClassPath. Thanks Stuart for keeping >> me >> honest and letting me know that what I was trying to do in principle was >> right! >> > > Well, those should be case insensitive, I would think. At least the > framework treats them that way, so tooling should too, I think. > Recent builds of Bnd (at least since 0.0.357 which is the version used in bundleplugin 2.0.1) treat framework headers like Bundle-ClassPath as case-sensitive (and warns if you use the "wrong" case) but there may be some places in the bundleplugin which need tweaking too. > -> richard > > > Cheers, >> Craig >> >> On Mon, Feb 1, 2010 at 11:07 PM, Stuart McCulloch<[email protected]> >> wrote: >> >> >> >>> On 2 February 2010 12:48, Craig Ching<[email protected]> wrote: >>> >>> >>> >>>> On Mon, Feb 1, 2010 at 10:41 PM, Stuart McCulloch<[email protected]> >>>> wrote: >>>> >>>> >>>> >>>>> On 2 February 2010 04:00, Ching, Craig<[email protected]> wrote: >>>>> >>>>> >>>>> wrt. automatically setting the Export-Package list from the packages in >>>>> embedded jar >>>>> neither the bundleplugin or Bnd Tool do this - the bundleplugin sets >>>>> Export-Package to >>>>> be the list of packages in your source directories, unless you set it >>>>> explicitly >>>>> >>>>> what you're doing above is basically what the bundleplugin >>>>> >>>>> >>>> Embed-Dependency >>>> >>>> >>>>> instruction >>>>> does (the code I linked to in my earlier post does nothing to the >>>>> Export-Package settings) >>>>> >>>>> perhaps you want to use the -exportcontents instruction? this has a >>>>> >>>>> >>>> similar >>>> >>>> >>>>> effect on the >>>>> exported packages as Export-Package, but with one important difference: >>>>> >>>>> >>>> it >>>> >>>> >>>>> doesn't pull >>>>> classes into the bundle or affect the contents, it just alters the >>>>> >>>>> >>>> exported >>>> >>>> >>>>> packages >>>>> >>>>> for example: >>>>> >>>>> Export-Package: * >>>>> >>>>> inlines all classes/resources on your classpath >>>>> >>>>> whereas: >>>>> >>>>> -exportcontents: * >>>>> >>>>> export all packages contained in the bundle without affecting the >>>>> >>>>> >>>> contents >>>> >>>> >>>>> >>>>> >>>> I did try -exportcontents, but I think I did -exportcontents=* and that >>>> resulted in the jar being inlined (i.e. expanded in the resulting >>>> >>>> >>> bundle). >>> >>> >>>> I'll try what you suggest. >>>> >>>> >>>> >>> Well -exportcontents should never inline anything - it only updates the >>> list >>> of exported packages. >>> I think something else was going on, I've successfully used >>> Include-Resource, Bundle-ClassPath >>> and -exportcontents to embed JARs and export their packages without >>> anything >>> being inlined. >>> >>> >>> >>>> >>>> >>>>> now if the jars you're embedding are bundles and you want their >>>>> Export-Package settings >>>>> combined in the mega-bundle then neither the Bnd Tool or the >>>>> >>>>> >>>> bundleplugin >>> >>> >>>> support this, >>>>> but it might be possible to add it as a feature (to either Bnd or the >>>>> bundleplugin) >>>>> >>>>> >>>>> >>>>> >>>> Nope, these are bare jar files, not bundles. I wish they were bundles >>>> >>>> >>> ;-) >>> >>> >>>> >>>> >>>> >>>>> >>>>> >>>>>> Cheers, >>>>>> Craig >>>>>> >>>>>> >>>>>> >>>>> -- >>>>> Cheers, Stuart >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> -- >>> Cheers, Stuart >>> >>> >>> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
