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. > > 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 >
