[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- From: Scott Lewis <slewis@xxxxxxxxxxxxxxxxx>
- Date: Mon, 30 Mar 2009 10:14:48 -0700
- Delivered-to: firstname.lastname@example.org
- User-agent: Thunderbird 22.214.171.124 (Windows/20090302)
Ian Bull wrote:
CUs are just IUs that describe configuration actions. If there are no
CUs inserted on export this is mostly likely the issue. Are there
really no CUs in the metadata, or are they just not getting executed
(i.e. because of incompatible platform filters)?
As far as I can tell, it seems that there are no CUs added to the
metadata (I've been searching for 'tooling' in resulting content.xml and
can't find any associated with the features that I export (i.e. via the
PDE export deployable feature). I *do* find the features/bundles
themselves, but nothing with 'tooling' prefix as expected.
I thought I would try to use the publisher to generate metadata for the
feature instead of the export deployable feature wizard...and see if
that makes a difference.
On Mon, Mar 30, 2009 at 9:42 AM, Scott Lewis <slewis@xxxxxxxxxxxxxxxxx
Pascal Rapicault wrote:
For bundles to be installed in OSGi, a CU indicating to do so
needs to be attached to the IU representing the bundle.
Most of the time, the tooling.osgi.bundle.default CU is all
you need since it just installs a bundle at start level 4 and
does not start it.
This attachment is represented by a ResolvedIU which has the
original IU and the additional fragments.
Note that normally the planned returned by the director will
contain the proper attachment if of course the CUs had been
passed to it.
It seems my (remote) planner is not adding the tooling CU's to the
operands that it sends for the engine to execute. I notice from
looking through the director code that for director runs this is
done via the planner.getProvisioningPlan...i.e.
result = planner.getProvisioningPlan(request, context, new
How is the adding of the CU's triggered within the planner? Are
they just retrieved from the metadata repo? I've been using the
feature export of the PDE, and noticed that when I export a
deployable feature to an existing repo...although it puts the
actual IUs in there, it doesn't create/put any tooling CUs in the
target repo. Could this be the issue? How does one create these
tooling CUs in the repo (if that's what's needed)?
p2-dev mailing list
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource
p2-dev mailing list