[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- From: Scott Lewis <slewis@xxxxxxxxxxxxxxxxx>
- Date: Mon, 30 Mar 2009 10:58:55 -0700
- Delivered-to: firstname.lastname@example.org
- User-agent: Thunderbird 22.214.171.124 (Windows/20090302)
Although I'm ready to try out using the generator to create the CUs, I
had the impression that the generator was deprecated/going away. Please
correct if this is wrong.
I've just tried the FeaturesAndBundlesPublisher, and it does *not* seem
to generate the CUs either...and I can't find an option for the app that
sounds like the right thing.
For deployable feature exports (as opposed to product exports...which
*do* seem to generate CUs), is there now an approved/other way to
The way I achieved this was to create a root feature, using the p2
generator. This root feature then required these "tooling" CUs and thus
they got added to the generated repo. When I installed this root
feature, using the director, the CUs also got added to the local p2
profile and subsequent bundle provisioning operations into this profile
then worked because the CUs got attached to the bunldes being installed
- which ultimately meant that the p2 engine could create the right set
of install actions - namely the parameterized install action.
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On
Behalf Of Scott Lewis
Sent: 30 March 2009 17:43
To: P2 developer discussions
Subject: Re: [p2-dev] p2 Engine
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.it.
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
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
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
p2-dev mailing list
p2-dev mailing list