Eclipse Community Forums: Rich Client Platform (RCP)

Help

Home

Home » Eclipse Projects » Rich Client Platform (RCP) » RCP update site problem

Show: Today's Messages :: Show Polls :: Message Navigator

RCP update site problem [message #482368]

Wed, 26 August 2009 11:32

Christian Pontesegger

Messages: 250
Registered: July 2009
Location: Graz, Austria

Senior Member

Hi,

I am working on an update site for my RCP app and I ran into a problem
where I need your help:

My app consists of 3 features: core, basic_tool, advanced_tool

core: holds the application
basic_tool: an extension which is optional
advanced_tool: another optional extension. this feature includes feature
basic_tool

now a user installs basic_tool - which works

Some time later all features get updated on the update site.

Now when the user tries to install advanced_tool, he would require to
update basic_tool too (as installer reports a conflicting dependency
between the old version of basic_tool and the new one to be installed)

If the user updates basic_tool beforehand, everything works as expected.

Is there a way that the update is done automatically when advanced_tool is
selected? I don't want the user to take care of this (as it gets far more
complex in reality).

thanks
Christian

Report message to a moderator

Re: RCP update site problem [message #482976 is a reply to message #482368]

Fri, 28 August 2009 19:04

Mario Winterer

Messages: 136
Registered: July 2009

Senior Member

Christian,

I'm not sure, but I think you should change feature "advanced_tool" to
require "basic_tool" instead of including it.
(See "dependencies" page of the feature manifest editor).

Mario

"Christian Pontesegger" <christian.pontesegger@web.de> schrieb im
Newsbeitrag news:4de41284655a6a2d774f8c0e995c4839$1@www.eclipse.org...
> Hi,
>
> I am working on an update site for my RCP app and I ran into a problem
> where I need your help:
>
> My app consists of 3 features: core, basic_tool, advanced_tool
>
> core: holds the application
> basic_tool: an extension which is optional
> advanced_tool: another optional extension. this feature includes feature
> basic_tool
>
> now a user installs basic_tool - which works
>
> Some time later all features get updated on the update site.
>
> Now when the user tries to install advanced_tool, he would require to
> update basic_tool too (as installer reports a conflicting dependency
> between the old version of basic_tool and the new one to be installed)
>
> If the user updates basic_tool beforehand, everything works as expected.
>
> Is there a way that the update is done automatically when advanced_tool is
> selected? I don't want the user to take care of this (as it gets far more
> complex in reality).
>
> thanks
> Christian
>

Report message to a moderator

Previous Topic:	Selection provider that is not a workbench part
Next Topic:	Application startup problem in 3.2 with login dialog before workbench start on first launch only

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Jan 14 04:29:06 GMT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter