While creating the sample, I noticed very strange behavior and due to which I am somewhat stuck. I will explain the problem in 2 scenarios
Now export the deployable feature and copy the generated files into webserver.
Open install new software option and install the 2nd feature using the URL.
The feature gets installed and even gets updated with every build.
Export the product and test it using the generated launcher. Everything works fine.
Now export the deployable feature and copy the generated files into webserver.
Open install new software option and update the application using the URL.
The updater complains as the feature is already installed and update will be performed instead.
Unfortunately the update doesn't work and the step shows error as:
Your original request has been modified.
"Mail Protection" is already installed, so an update will be performed instead.
"Core" is already installed, so an update will be performed instead.
Cannot complete the install because of a conflicting dependency.
Software being installed: Mail Protection 1.0.0.201103061657 (com.example.mail.protection.feature.group 1.0.0.201103061657)
Software currently installed: RCP Product 1.0.0.201103061656 (com.example.mail.product 1.0.0.201103061656)
Only one of the following can be installed at once:
Mail Protection 1.0.0.201103061656 (com.example.mail.protection.feature.jar 1.0.0.201103061656)
Mail Protection 1.0.0.201103061657 (com.example.mail.protection.feature.jar 1.0.0.201103061657)
Cannot satisfy dependency:
From: RCP Product 1.0.0.201103061656 (com.example.mail.product 1.0.0.201103061656)
To: com.example.mail.protection.feature.group [1.0.0.201103061656]
Cannot satisfy dependency:
From: Mail Protection 1.0.0.201103061656 (com.example.mail.protection.feature.group 1.0.0.201103061656)
To: com.example.mail.protection.feature.jar [1.0.0.201103061656]
Cannot satisfy dependency:
From: Mail Protection 1.0.0.201103061657 (com.example.mail.protection.feature.group 1.0.0.201103061657)
To: com.example.mail.protection.feature.jar [1.0.0.201103061657]
This seems to be surprising as update works when I install the feature after the product has been exported.
But if the feature is already bundled with the product, then the updates to the feature are not working.
Do you know why?
I had the same problem but i figured it out. The problem is the base plugins that are bundled with product can't be updated if we export them as a deployable features or build them through update site. The only way is to re-export your product(from product configuration) and copy the required base plugins and feature from the export folder into web server. Now check for updates again, you will see your updated base feature and updated product version in the list. You can't update only you base feature, you have to update both(feature and product). This was the show stopper and now it works for me.