[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] New Module support.

I noticed that the Export-Module entry value for automatically generated manifests contains the bundle name as its first element (see manifest generated for the resources plug-in below). Will it always be equal to the bundle name? I don't have a problem with redundancy, I was just wondering if I can rely on the bundle name to determine the module id.

Generated: true
Bundle-Name: org.eclipse.core.resources
Bundle-Version: 3.0
Bundle-ClassPath: resources.jar
Legacy: true
Bundle-Activator: org.eclipse.core.runtime.compatibility.PluginActivator
Plugin-Class: org.eclipse.core.resources.ResourcesPlugin
Export-Module: org.eclipse.core.resources; module-version=3.0;
DynamicImport-Package: *

Thomas Watson <tjwatson@xxxxxxxxxx>
Sent by: equinox-dev-admin@xxxxxxxxxxx

25/09/2003 06:59 PM

        To:        equinox-dev@xxxxxxxxxxx
        Subject:        [equinox-dev] New Module support.

New module support has been dropped into the Equinox repository.  The new
module support should replace all of the package splitting that was being
done.  As a result all of the hard-coded manifests need to be updated for
the following standard plugins:


The equinox plugin project org.eclipse.core.runtime.osgi contains the
updated manifests for these projects under the folder
org.eclipse.core.runtime.osgi/manifests/.  All other standard plugins
should remove their existing manifest files so that the new manifest
generator will create the properly formated ones.  The following standard
plugins currently have manifests that need to be deleted:


Until a new integrated build includes these manifest changes you will need
to manually update or remove the manifests for the plugins mentioned above.

Thomas Watson

equinox-dev mailing list