Pascal, Thanks for pointing this out. The provisioning actions seem to be the right path for me. I've got a bunch of questions: 1. I didn't understand how to view the output of your example - it outputs everything to System.out instead of Eclipse log. Is there a way I can debug provisioning actions from PDE? 2. ProvisioningAction moved to other package in Eclipse 3.6+. Does that mean that I'll need to provide two separate plugins for 3.5 and 3.6+? 3. Does the feature that runs install action need to be separate from feature that contains the plugin with action implementation, like in your example? Can I put p2.inf only to 1 plugin and 1 feature that contains it? (or maybe even just to plugin??)
Thanks again, Andrey 2011/3/30 Pascal Rapicault <[email protected]>: > The installer handlers are replaced by a combination of two concepts: > - touchpoint, touchpoint actions, that allows to run code as part of the > execution > - metarequirements that are usually carried by the IU that uses this actions > and thus helps in making sure that the action is properly installed before > the installation proceeds. > > Here is an example attached. > > > > On 2011-03-25, at 7:04 AM, Andrey Razumovsky wrote: > >> Hi, >> >> I noticed that all org.eclipse.update.core bundle and InstallHandler >> in particular were deprecated, but the description is very poor. How >> can I implement install handler for my plugin/feature using Equinox >> API? Can I have a simple example of p2.inf? >> >> Thanks, >> Andrey >> _______________________________________________ >> p2-dev mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/p2-dev > > > _______________________________________________ > p2-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/p2-dev > > _______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
