[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] A working example of custom p2 provisioning action
- From: Борислав Капукаранов <b.kapukaranov@xxxxxxxxx>
- Date: Sun, 29 May 2011 22:07:24 +0300
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ejsYMi3wxyQObYNkcXSCbXo78YLT0lmPFT7WzikUhirjMHFa8M5tLWcSoZ3c4CSI5t g57UHnY6YGnYg/4SY1OAMig19ne/7xDFCcB1W7Ho5sLgBaLkMGBmZ9GLsJbpv7qJFbYU s0qtzeIMAEZjj+2o+19Vq90RRWjyulNi4iLh4=
If you go the "own touchpoint" route you basically can take a look at EclipseTouchpoint and see how its done there.
You don't need all the stuff - the initializeOperand is something you'll need. Also take a look at p2.touchpoint.eclipse's plugin.xml - you'll need something similar for your touchpoint and the actions it'll provide.
Another thing to keep in mind is that you'll have to define a CollectAction along your custom one as that one is mandatory. Again you can take a look at how its done in Eclipse.
Basically the best advice i think is to comparatively debug as you implement your stuff and see whats missing from the standard operation you can find with p2.touchpoint.eclipse.
2011/5/29 Борислав Капукаранов <b.kapukaranov@xxxxxxxxx>
Probably its best to start by taking a look at the provisioning actions provided in the "org.eclipse.equinox.p2.touchpoint.eclipse" project.
They are quite good example if you want to learn how its done :)
If you are seeking to provide custom provisioning action i think you have two options:
1. You can either enhance the p2.touchpoint.eclipse by just include your prov action in there and describe it in p2.touchpoint.eclipse's plugin.xml file. (probably the easier one but you end up with customized standard bundle which is not the best solution)
2. Provide your own touchpoint (this is where all the fun is :) )
I’m trying to write a custom p2 provisioning action to execute my own code when installing feature. I haven’t found any docs on this topic in the web, and it’s hard to debug because eclispe silently ignores me (even in a log). The only example I’ve found is here: http://dev.eclipse.org/mhonarc/lists/p2-dev/msg04002.html, but it seems not working (I cannot install plugins provided in 3.6.2).
So, if somebody can point me at a working example of custom provisioning action, that would help me understand the whole thing.
p2-dev mailing list