Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Talk:Equinox/p2/Adding Self-Update to an RCP Application
< Talk:Equinox
Revision as of 09:25, 10 June 2010 by Tjodes.vitaphone.de (Talk | contribs) (New page: *I'm interested in a headless update as described in here on top of Eclipse 3.6 (RC3) & Equinox 3.6 (RC3). In order to do so, I created a 3.6 target platform and defined my applicatio...)
- I'm interested in a headless update as described in here on top of Eclipse 3.6 (RC3) & Equinox 3.6 (RC3).
In order to do so, I created a 3.6 target platform and defined my application based upon features, included o.e.e.p2.ui.sdk and the org.eclipse.equniox.p2.autoupdate (new new one based upon equinox 3.6 operations api,not the one found via ralf ebert's tutorial)
| Question 1: Is it possible to facilitate testing during development, so that I have a valid p2 folder starting the osgi platform in development mode right out of eclipse? If yes, how can I set up this? Right now, I can only test when I export my product every time, so that the "p2 ecosystem" created. But you cannot debug P2 api call stack then (with eclipse debugger) |
| Question 2: Assume you have a working product consisting of 3 features. Is it possible to write an automatic headless update, that modifies the product as a whole, i.e. adding 2 completely new features, replacing an old one etc. If yes, any examples / clues are welcome. |
| Question 3: Is it possible via a headless automatic update to replace a config.ini with all its parameters etc.? If yes, how ;)? |