[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Inconsistencies in the runtime plugin.xml and manifest.mf files

I have updated org.eclipse.core.runtime and org.eclipse.core.runtime.compatibility to remove the bundle manifest files.  The bundle manifest files will be generated by the manifest generator.  The runtime is only re-exporting org.eclipse.osgi.  The runtime.compatibility is re-exporting runtime, all three osgi bundles, and update.configurator.

I did not change this since I'm not sure how the rest of eclipse is using these re-exported plugins from runtime.compatibililty.

Thomas Watson
Pervasive Development
Phone: 512-838-4533 Tie: 678-4533

Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>
Sent by: equinox-dev-admin@xxxxxxxxxxx

02/15/2004 10:09 PM

        To:        equinox-dev@xxxxxxxxxxx
        Subject:        [equinox-dev] Inconsistencies in the runtime plugin.xml and manifest.mf files

I noticed that the runtime plugin.xml does not re-export org.eclipse.osgi.services or org.eclipse.osgi.utils but does re-export org.eclispe.osgi itself.  Interestingly, the runtime manifest.mf does requires only org.eclipse.osgi. (and re-exports it)

runtime.compatibility requires and re-exports all three osgi bundles in both the plugin.xml and the manifest.mf but its plugin.xml requires org.eclipse.update.configurator but this is not included in the manifest.mf.

So, there are inconsistencies between runtime and compatibility (still don't understand why runtime does not reexport all three osgi bundles) and inconsistencies between the plugin.xml and manifest.mf for both runtime and runtime.compatibility