[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Re: Why is org.eclipse.osgi marked as Eclipse-ExtensibleAPI


The org.aspectj.osgi framework extension bundle in the Aspects Equinox Incubator needs AspectJ, which comprises two bundles, but obviously cannot import the necessary packages so it uses them though a new service bundle. However,  it needs to export a service interface and if the Eclipse-ExtensibleAPI: true  is not used the service bundle will not compile.

Matthew Webster
AOSD Project
Java Technology Centre, MP146
IBM United Kingdom Limited
Hursley Park, Winchester,  SO21 2JN, England
Telephone: +44 196 2816139 (external) 246139 (internal)

Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

29/03/2007 07:20

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

[equinox-dev] Re: Why is org.eclipse.osgi marked as        Eclipse-ExtensibleAPI

Pascal Rapicault wrote:
> Could someone remind me why the manifest of org.eclipse.osgi contains the
> mark up Eclipse-ExtensibleAPI: true

AFAIK because it's the system bundle and you can create fragments for it
which export additional packages that are available on the system
classpath and that should be made available to all other bundles.

For example, in a J2EE container were you are using the servlet bridge
you would add fragments to export packages that are available from the
WAR or the container.

Cu, Gunnar

Gunnar Wagenknecht

equinox-dev mailing list

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU