An "aggregator" bundle is used to pull together the parts of a split package
and export the whole package. It uses Require-Bundle to pull in the pieces
and then exports the package without any attributes.
For example, suppose package com.foo is split across bundles A and B. Both A
and B use mandat
>
> Is adding the split attribute to the Import-Package really the best
> solution? It assures that the importer gets only part of the package, and it
> also makes a
>
No, I would suggest to fall back to importing the o.e.ui bundle.
> mess of the manifest. Surely it's better to ensure that an a
Is adding the split attribute to the Import-Package really the best
solution? It assures that the importer gets only part of the package, and it
also makes a mess of the manifest. Surely it's better to ensure that an
aggregating bundle exists... then importers can simply import org.eclipse.ui
witho
Hi Simon and Thomas,
Thanks for your help. After Thomas explained the problem I found a blog
about split packages. To help future lost souls, it is here [1].
Best regards,
Wim
[1]
http://eclipsesource.com/blogs/2009/07/14/why-i-cant-recommend-using-import-package/
On Wed, Sep 8, 2010 at 5:34 A
If you look at the exports of the two packages from the org.eclipse.ui
bundle you will notice the following for the org.eclipse.ui and
org.eclipse.ui.part package exports:
ui.workbench=split;mandatory:="ui.workbench"
This indicates that the packages org.eclipse.ui and org.eclipse.ui.part are
spl
Wim
I agree that that makes little sense. Can you please show us each of the
bundles in this problem using the "bundle" command, and the manifests for
these bundles using the "headers" command.
Thanks
Simon
From:
Wim Jongman
To:
OSGi Developer Mail List
Date:
09/07/2010 02:28 PM
Subject:
