Stuart McCulloch wrote:
On 18/03/2008, Alin Dreghiciu <[EMAIL PROTECTED]> wrote:
I "especially" requested that from Peter K a while ago. Mainly my
request was related to not export META-INF if you used * in
Export-Package instruction, if I recall it correctly.
FYI, Peter has recently released a new version of Bnd, 0.0.239:
Allow export of specifically mentioned metadata packages like META-INF.
These are normally not exported but sometimes it is necessary. There is
no wildcard expansion for these dirs.
I'll try to get this into the next release of the bundleplugin (1.4.1)
Thanks Stuart.
--G
The reasoning
was related to how are you going to use such a package if there is
more then one bundle that exports it as it has no name space related
to it. To what exporter will your importing bundle get wired? More,
your bundle that imports the META-INF will only be wired to one
exporter as split packages are only possible with Require-Bundle.
Alin
On Wed, Mar 19, 2008 at 1:46 AM, Guillaume Sauthier
<[EMAIL PROTECTED]> wrote:
Hi all
I've an issue with Bnd (in maven-bundle-plugin): I want to export the
META-INF "package", because some files that are inside are searched by
external applications (not to name them : JSF impl) and, even when I
explicitely put Export-Package META-INF in my .bnd file, they never
show
up in my resulting Manifest.
I'm not 100% sure about that, but I never read that exporting that
special entry was forbidden in OSGi. This is a best practice that is
enforced by Bnd when building the bundle Manifest :)
Does someone has a trick to export the META-INF ? Or maybe that's
forbidden ?
Cheers
--Guillaume
