|
Re: custom p2 touchpoint actions with a signed update site [message #499168 is a reply to message #499166] |
Fri, 20 November 2009 09:09 |
Eclipse Developer Messages: 3 Registered: November 2009 |
Junior Member |
|
|
A little more info:
PLUGIN ONE has a p2.inf file in META-INF as below:
provides.0.namespace=org.eclipse.equinox.p2.engine.actions
provides.0.name=my.installAction
provides.0.version=1.0.0
provides.1.namespace=org.eclipse.equinox.p2.engine.actions
provides.1.name=my.uninstallAction
provides.1.version=1.0.0
The actions are contributed by the org.eclipse.equinox.p2.engine.actions extension point for the org.eclipse.equinox.p2.osgi touchpoint type in this plugin.
FEATURE ONE has a p2.inf file at the root as below:
metaRequirements.0.namespace=org.eclipse.equinox.p2.engine.a ctions
metaRequirements.0.name=my.installAction
metaRequirements.0.range=1.0.0
metaRequirements.1.namespace=org.eclipse.equinox.p2.engine.a ctions
metaRequirements.1.name=my.uninstallAction
metaRequirements.1.range=1.0.0
instructions.install=my.installAction();
instructions.uninstall=my.uninstallAction();
NOTE:
I do not use instructions.<phase>.import as I am using fully-qualified names to reference my actions. These work in most conditions, but not all (see the first post).
|
|
|
Powered by
FUDForum. Page generated in 0.02519 seconds