Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Rich Client Platform (RCP) » Re: RCP app failing to update in 3.5
Re: RCP app failing to update in 3.5 [message #490445] Thu, 08 October 2009 16:25 Go to next message
Benjamin Zeiss is currently offline Benjamin Zeiss
Messages: 29
Registered: July 2009
Junior Member
Hi,

I am experiencing similar problems. However, i in fact use the
..qualifier technique and i replace the qualifiers of all manifests,
..product files, and features before i call the antrunner for the
headless product build. I also checked that the content.xml doesn't have
any unreplaced .qualifiers in there - they are all replaced.

Another thing that i noticed is that the p2.inf next to the product file
contains my default repository (using the addRepository stuff). This
default repository appears when i make a manual export from the Eclipse
GUI (product file editor) from my Windows machine. When i build my
product headless on the Linux machine, the default repositories are
missing. I tried the fully qualified name, but no luck.

Are these problems somehow related? The only thing that i could think of
that i do differently is that i use a category.xml file for the headless
Linux build. However, if i remove it, the update still doesn't work.

How can i even begin to debug problems like these? I am totally clueless
and don't know what to look for...and this is already day two for me
fiddling with the p2/update stuff.

Another thing i was wondering about: can i securely delete my repository
at some point or does it brake the update functionality with previous
versions that used to be in there? i don't necessarily want to keep all
my daily builds around...

Any help is greatly appreciated!

Ben


Andrew Niefer schrieb:
> 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
>>
>>
Re: RCP app failing to update in 3.5 [message #490507 is a reply to message #490445] Thu, 08 October 2009 20:55 Go to previous message
Benjamin Zeiss is currently offline Benjamin Zeiss
Messages: 29
Registered: July 2009
Junior Member
Hh my, i just found out the reason why my repositories weren't listed.
The installer that i build with Linux installs by default to "c:\Program
Files (x86)" and from Vista on, Windows won't write to these folders.
Without write permissions, it seems, Eclipse/P2 decides to simply not
list the sites from the added repositories without giving any hint about it.

Now i am wondering what the right approach to solve this problem is.
Tune the installer to give write access to this directory, simply check
that the selected folder will have sufficient write permissions or maybe
tune Eclipse to install plugins elsewhere somehow? Is there any standard
solution for this?

I still have the problem that my product won't be updated.

Ben

Benjamin Zeiss schrieb:
> Hi,
>
> I am experiencing similar problems. However, i in fact use the
> .qualifier technique and i replace the qualifiers of all manifests,
> .product files, and features before i call the antrunner for the
> headless product build. I also checked that the content.xml doesn't have
> any unreplaced .qualifiers in there - they are all replaced.
>
> Another thing that i noticed is that the p2.inf next to the product file
> contains my default repository (using the addRepository stuff). This
> default repository appears when i make a manual export from the Eclipse
> GUI (product file editor) from my Windows machine. When i build my
> product headless on the Linux machine, the default repositories are
> missing. I tried the fully qualified name, but no luck.
>
> Are these problems somehow related? The only thing that i could think of
> that i do differently is that i use a category.xml file for the headless
> Linux build. However, if i remove it, the update still doesn't work.
>
> How can i even begin to debug problems like these? I am totally clueless
> and don't know what to look for...and this is already day two for me
> fiddling with the p2/update stuff.
>
> Another thing i was wondering about: can i securely delete my repository
> at some point or does it brake the update functionality with previous
> versions that used to be in there? i don't necessarily want to keep all
> my daily builds around...
>
> Any help is greatly appreciated!
>
> Ben
>
>
> Andrew Niefer schrieb:
>> 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
>>>
>>>
Previous Topic:PreferencePage via org.eclipse.ui.window.preferences: AssertionFailedException
Next Topic:p2.inf/addRepository and no write permissions in c:\program files
Goto Forum:
  


Current Time: Sat Oct 25 02:58:41 GMT 2014

Powered by FUDForum. Page generated in 0.09926 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software