[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Eclipse-ExtensibleAPI Manifest Header


The Eclipse-ExtensibleAPI header is not used at runtime at all.  The OSGi Framework supports this by default.  Fragment bundles are allowed to add packages to the host bundle by default in OSGi.

This header is only used by PDE at development time.  PDE's classpath container uses this header to indicate that fragments of an extensible host bundle must be added to the classpath of bundles that import/require packages from the host bundle.  The only reason you should add this header to your host bundle is to improve your development experience with PDE when working with such bundles.

Tom





"Jeremy Volkman" <jvolkman@xxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

11/08/2006 04:04 PM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To
"Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>
cc
Subject
[equinox-dev] Eclipse-ExtensibleAPI Manifest Header





I recently came across a situation in which I wanted to organize a
large and messy web-UI bundle into a core bundle and some additional
fragments.  Most of the fragments provide packages in addition to
those provided by the core bundle.  I was excited to find the
Eclipse-ExtensibleAPI manifest header which seems to fill this need.
>From the docs:

The Eclipse-ExtensibleAPI is used to specify whether a host bundle
allows fragment bundles to add additional API to the host. This header
should be used if a host bundle wants to allow fragments to add
additional packages to the API of the host. If this header is not
specified then a default value of 'false' is used.

Is there anything like this in the official OSGi spec? If not, is
there any chance that this feature will make it into the next spec
version?

Thanks,
Jeremy Volkman
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev