In my experience it is necessary to include the p2 features directly in the product:
You can either include them in your feature [1].
Or include them directly in your product file [2].
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 [1] 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!
Cheers,
Hugues
On Fri, Aug 5, 2011 at 4:58 PM, Pradeep Fernando
<pradeepfn@xxxxxxxxx> wrote:
Hi devs,
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
config.ini.
Any Suggestions, pointer will be greatly appreciated.
thanks,
--Pradeep
here is my .product file content.
<product name="Example Product" uid="example.product.id"
id="example.product" application="example-bundle.application"
version="1.0.0.SNAPSHOT" useFeatures="true" includeLaunchers="true">
<configIni use="default">
</configIni>
<launcherArgs>
</launcherArgs>
<plugins>
</plugins>
<features>
<feature id="example-feature" version="0.0.0"/>
</features>
<configurations>
<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
org.eclipse.equinox.p2.publisher.eclipse.ConfigCUsAction#publishBundleCUs)
-->
<property name="org.eclipse.update.reconcile" value="false" />
<plugin id="org.eclipse.update.configurator" autoStart="true"
startLevel="4"/>
</configurations>
</product>
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev