[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[p2-dev] Cannot update my product after migrating to Eclipse 3.5/p2/Buckminster build

Hi,
I recently migrated my RCP application from a 3.4.2 to 3.5.2 target. Product building happily on multiple platforms with Buckminster and p2 director. There was some learning curve involved with that, but overall I am very happy with the improvements to our build process and configuration.

However, I am close to releasing my product and now having a serious blocker with getting my product to update. When I create an update site, I am unable to update the product itself through the update site. This was possible with our earlier (pre-p2) update mechanism.

Our product consists of a single top-level feature (includes sub-features and required plugins that comprise the core application). The update site is a separate feature that includes the product feature and some additional optional ones. The optional features install no problem, but when I try to update the main product feature through the UI with "Check for Updates", no updates are found. When I try "Install New Software", the feature seems to recognize an update should be performed but configuration fails fails with:

Your original request has been modified.
ÂÂ"BladeLogic Application Release Automation Feature" is already installed, so an update will be performed instead.
ÂÂ"BIRT Runtime for BladeLogic Applications" is already installed, so an update will be performed instead.
ÂÂ"BladeLogic Application Release Automation Team Feature" is already installed, so an update will be performed instead.
Cannot complete the install because of a conflicting dependency.
ÂÂSoftware being installed: BladeLogic Application Release Automation Feature 3.7.1.16000_201006281830 (com.phurnace.deliver.feature.feature.group 3.7.1.16000_201006281830)
ÂÂSoftware currently installed: Deliver 3.7.1 (com.phurnace.deliver.ui.product 3.7.1)
ÂÂOnly one of the following can be installed at once:Â
ÂÂ ÂBladeLogic Application Release Automation Feature 3.7.1.15000_201006281812 (com.phurnace.deliver.feature.feature.jar 3.7.1.15000_201006281812)
ÂÂ ÂBladeLogic Application Release Automation Feature 3.7.1.16000_201006281830 (com.phurnace.deliver.feature.feature.jar 3.7.1.16000_201006281830)
ÂÂCannot satisfy dependency:
ÂÂ ÂFrom: BladeLogic Application Release Automation Feature 3.7.1.15000_201006281812 (com.phurnace.deliver.feature.feature.group 3.7.1.15000_201006281812)
ÂÂ ÂTo: com.phurnace.deliver.feature.feature.jar [3.7.1.15000_201006281812]
ÂÂCannot satisfy dependency:
ÂÂ ÂFrom: BladeLogic Application Release Automation Feature 3.7.1.16000_201006281830 (com.phurnace.deliver.feature.feature.group 3.7.1.16000_201006281830)
ÂÂ ÂTo: com.phurnace.deliver.feature.feature.jar [3.7.1.16000_201006281830]
ÂÂCannot satisfy dependency:
ÂÂ ÂFrom: Deliver 3.7.1 (com.phurnace.deliver.ui.product 3.7.1)
ÂÂ ÂTo: com.phurnace.deliver.feature.feature.group [3.7.1.15000_201006281812]

I have tried incrementing the micro revision as well, same result.ÂIt seems from researching this issue, p2 does not handle updating the product platform in the same way that it does updating an optional feature. However, this is exactly what I need -- I want the user to be able to update the product in the same manner.

Pre-p2, the update mechanism would simply copy the new plugins and features side-by-side with the old ones into the product installation, and Equinox would load the latest version on next startup. How do I (can I?) get p2 to do this, or something equivalent? How do I configure my update site for product updates?

I've tried playing with p2.inf settings, director options, but I'm flying blind here.

Please advise,
Casey