|Re: Tutorial: p2 updates for Eclipse RCP applications [message #498630 is a reply to message #493450]
||Tue, 17 November 2009 17:44
Registered: July 2009
|Ralf Ebert wrote on Mon, 26 October 2009 06:51|
I just wrote a tutorial about how to use the Equinox p2 provisioning
system for updating Eclipse RCP applications:
Thought you might be interested in this and would be glad to hear your
Thanks for the tutorial!
I just tried to go through it step by step and have a problem in your "Add self-update to the application" section. I will list your steps ad show what failed
Step 1, which was to create the p2.inf file, worked fine.
Step 2, deleting the old exported folder and deploying the product again - also worked fine. Launching the newly exported app and checking for updates told me there were no updates available.
Step 3 - Like you said to do, I made some visible changes to the Main email view (added 2 labels)
Step 4 - I incremented the version number in the plugin, feature, and product, and told the product to use the updated version of the feature.
Step 5 - I renamed the old applications folder from "eclipse" to "mail_old" like you instructed. I left the repository directory there unchanged. I then exported the application again
Step 6 - Starting the newly exported application, I verified that my Labels were present in the view to see that my product was in fact updated correctly
Step 7 - I started the old version in the "mail_old" directory and selected "Check For Updates" from the Help menu. It told me there were no updates to install
Your instructions said it should see updates at this point. The "mail_old" directory is in the same directory as the newly exported "eclipse" directory containing the application and the "repository" directory that contains the "older" repository information and the updated repository information. Did I miss something?
How can I update the "com.example.mail.core" feature and "com.example.mail" plugin in the same way as the "com.example.mail.protection" feature? I exported the "com.example.mail.protection" feature the way you instructed earlier in the tutorial, and the application was able to install and later update the Spam Filter feature from a web server. Can I update the "com.example.mail.core" the same way? I tried exporting the "com.example.mail.core" feature as a deployable feature to the same directory on the web server, but the application didn't see it as an available update and gave an error when manually selecting it from the "Install New Software" menu item.
We currently have an eclipse application where all features are on an older eclipse update site on a web server. This includes our application's "main" feature and plugin." All can be updated via the update site. We're trying to figure out how to move to the new p2 provisioning system, but we can't seem to get everything working yet. So using the RCP Mail Example plugin as an example of what we want to do, we'd want to have both the spam filter feature and the "Core" Mail feature as installable features on a web server. How can we do this?
Powered by FUDForum
. Page generated in 0.16469 seconds