Re: [equinox-dev] Provide-Package vs Import-Package

[Simon J Archer <sarcher@xxxxxxxxxx>]

It seems that adding the header:

Bundle-ManifestVersion:
2

makes the PDE tooling use Export-Package
rather than Provide-Package; this is far from obvious.  If adding
a Bundle-ManifestVersion header (with the value 2) is so important, why
does the PDE tooling not provide an easy way to specify this?

Thanks

Simon

Simon J Archer/Raleigh/IBM@IBMUS
Sent by: equinox-dev-bounces@xxxxxxxxxxx

02/14/2006 09:54 PM

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

To	equinox-dev@xxxxxxxxxxx
cc
Subject	[equinox-dev] Provide-Package vs Import-Package

While using M4 today I noticed that the manifest's Runtime page for my
bundle showed nothing in its Export-Package list, even though I had correctly
use the Export-Package header in my manifest.mf to export a bunch of packages.
 I quickly found that using the PDE tooling to add to the editor's
"Export-Package" list resulted in a Provide-Package header instead
of an Export-Package header.  I also found this rather old bug report
that sort of explained things... 

        https://bugs.eclipse.org/bugs/show_bug.cgi?id=75214

Provide-Package does not seem to be part of OSGi R3 or R4, so I assume
that it's an Equinox specific header.  Can anyone explain what's going
on here, and whether the PDE tooling is going to be fixed to allow you
to correctly add OSGi Export-Package header values.

Thanks 

Simon

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