[news.eclipse.platform.rcp] Re: RCP app failing to update in 3.5

[Andrew Niefer <aniefer@xxxxxxxxxx>]

It seems like you don't have a higher version of the product itself 
available, only higher versions of the features that your product includes.

You still have the original product installed which will have explicit 
versions for the features it requires.  Then when you tried to install 
the new version of a feature, the product still requires the old one and 
you get conflicts between the old and new features.

What you want is to have DebriefNG 3.0.0, and then update to DebriefNG 
3.0.1.  One way to make this a bit simple would be to use a version of 
"3.0.0.qualifier" in the product file, and export would automatically 
change that to a timestamp, so subsequent exports of the product would 
be updateable to the next due to increasing version numbers.

-Andrew

ian mayo wrote:
> Hi all,
> I've got a 3.4 application that was using classic updates.
>
> I've switched to 3.5, and am now adopting p2.
>
> I build and export my feature-based product (including metadata 
> repository).
> I'm then unsure about how updates should work.
>
> I'm aware that the deploy stage creates a repository.  If I update the 
> software, and re-do the export phase an updated repository is created.
>
> If I open a deployed application, and select 'Check for updates', it 
> doesn't find anything ('there is nothing to update').  If I explicitly 
> add the repository (via the update section of preferences), no updates 
> are found, but if I 'install new software' and clear the 'group items by 
> category' option I can see the updated features.  If I then select 
> 'next', my app establishes that it's actually performing an update but 
> not an install, but then fails.
>
> The failure indicates it can't install the updated features, because my 
> application depends on the existing versions:
>
> ===========================
> Your original request has been modified.
>  "Combined Maritime Analysis Platform plugins" is already installed, so 
> an update will be performed instead.
>  "Debrief-specific plugins" is already installed, so an update will be 
> performed instead.
> Cannot complete the install because of a conflicting dependency.
>  Software being installed: Combined Maritime Analysis Platform plugins 
> 1.0.6.200907021610 (org.mwc.cmap.combined.feature.feature.group 
> 1.0.6.200907021610)
>  Software currently installed: DebriefNG 3.0.0 (DebriefNG 3.0.0)
>  Only one of the following can be installed at once:    
> org.mwc.cmap.combined.feature_root 1.0.5.200907021600
>    org.mwc.cmap.combined.feature_root 1.0.6.200907021610
>  Cannot satisfy dependency:
>    From: DebriefNG 3.0.0 (DebriefNG 3.0.0)
>    To: org.mwc.cmap.combined.feature.feature.group [1.0.5.200907021600]
>  Cannot satisfy dependency:
>    From: Combined Maritime Analysis Platform plugins 1.0.5.200907021600 
> (org.mwc.cmap.combined.feature.feature.group 1.0.5.200907021600)
>    To: org.mwc.cmap.combined.feature_root [1.0.5.200907021600]
>  Cannot satisfy dependency:
>    From: Combined Maritime Analysis Platform plugins 1.0.6.200907021610 
> (org.mwc.cmap.combined.feature.feature.group 1.0.6.200907021610)
>    To: org.mwc.cmap.combined.feature_root [1.0.6.200907021610]
> ============================
>
> I'd appreciate any tips on what is actually happening here. Do I have to 
> amend my product to say that it can take updates versions of it's features?
>
>
> cheers,
> Ian