|[3.6.1][P2] How to allow a product update ? [message #631801]
||Fri, 08 October 2010 19:53
| Christophe Fondacci
Registered: July 2009
I have recently migrated to 3.6.1, coming from 3.5.2. Since P2 has been released in 1.0, I switched the update mechanism of my RCP product to P2 since the UpdateUI is deprecated since 1992
After some hard work to understand the API concepts (P2 bundles, trackers, installable units, metadata repos, etc.) now I can :
* Export my product with metadata (OK)
* Trigger updates from my RCP product
* Generate update sites (same as before)
It works fine, except that my product could not get updated anymore ! (this is the only reason I use p2 : to update my product...) :
1. Check for updates leads to a "No update found"
2. Install new software sees my feature updates (as new software). Selecting it leads to error messages "Conflicting dependency". The weirdest thing to me is the first lines of the message :
'Your original request has been modified.
"my feature name" is already installed, so an update will be performed instead.
Browsed the web, found some articles from Andrew Niefer on the topic from 2009, don't know if they still are up to date.
From what I understood (please correct me) :
* exported products define a fixed feature release compiled at export time, that's why another feature release is not allowed (conflicting dependency)
* product is the only root "Installable Unit", that's why no update is found since only the feature is published to the update site that's why they couldn't be updated.
And now I am a bit lost. So here are my questions :
* I got no problem with updating the product instead of the feature (it's roughly the same in my case : my product is based on one feature containing everything), as long as I can do this with P2 through "Check for updates". Is there any way to publish a product update to an update site instead of a feature ?
* Is there any way to make the feature updatable from the PDE export UI or do I need to go for headless PDE builds, config files, ant scripts, etc ?
* I do not want to allow my users to make a "Install new software" so I need P2 to find UPDATES, is it possible ?
I am sure I am missing something, because I cannot imagine that it is that complex to get a simple product export which is updatable with P2.
Any help, idea, suggestion, article, comment, would help me a lot...
Thank you all,
Powered by FUDForum
. Page generated in 0.04872 seconds