[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] SimpleConfigurator/bundles.info not get created in the product structure
- From: Hugues Malphettes <hmalphettes@xxxxxxxxxxx>
- Date: Fri, 5 Aug 2011 17:25:35 +0800
- Delivered-to: firstname.lastname@example.org
In my experience it is necessary to include the p2 features directly in the product:
You can either include them in your feature .
Or include them directly in your product file .
I hope this helps.
With both techniques we end-up hardcoding the exact version of p2 and equinox used by the product.
I wish there was a way to have a looser coupling and I tried a variant of  where I simply 'require' the p2 features.
Unfortunately, p2-director would not generate the simple configurator in the case.
If someone knows how to do this let us know!
On Fri, Aug 5, 2011 at 4:58 PM, Pradeep Fernando <pradeepfn@xxxxxxxxx>
I'm trying to build a product configuration using p2 director.
First I wrote a simple bundle which only has an activator. Then I
created a feature that refers to the created bundle. then I,
1. published the features/bundles using featureAndBundlePublisher (i
put the feature and bundle in a directory and gave that directory as
the source to publisher) in to p2-repo
2. Published the .product file in to the same p2-repo.
3. Then I installed the product using the director application, by
giving the created p2-repo and the helios p2-repo as the repositories.
Things are working fine, except the generated config.ini file list
down the osgi bundles using osgi.bundles property.
I want to use simpleConfigurator in my product. I cant figure out,
what should i do to enable simpleConfigurator to appear in my
Any Suggestions, pointer will be greatly appreciated.
here is my .product file content.
<product name="Example Product" uid="example.product.id"
version="1.0.0.SNAPSHOT" useFeatures="true" includeLaunchers="true">
Â <configIni use="default">
Â Â Â<feature id="example-feature" version="0.0.0"/>
Â Â Â<plugin id="org.eclipse.core.runtime" autoStart="true" startLevel="4" />
Â Â Â<plugin id="org.eclipse.equinox.common" autoStart="true" startLevel="2" />
Â Â Â<plugin id="org.eclipse.equinox.ds" autoStart="true" startLevel="2" />
Â Â Â<plugin id="org.eclipse.equinox.p2.reconciler.dropins"
autoStart="true" startLevel="4" />
Â Â Â<plugin id="org.eclipse.equinox.simpleconfigurator"
autoStart="true" startLevel="1" />
Â Â Â<!-- Disable update manager. It seems as if this could be
achieved by the first line, but in
Â Â Â Â Â fact the second line sets reconcile to false (see
Â Â Â<property name="org.eclipse.update.reconcile" value="false" />
Â Â Â<plugin id="org.eclipse.update.configurator" autoStart="true"
p2-dev mailing list