Eclipse Community Forums: Rich Client Platform (RCP)

Home » Eclipse Projects » Rich Client Platform (RCP) » RCP self update

Wed, 12 May 2010 02:24

Eclipse User

Originally posted by: edmon70.gmail.com

Hello,

I have a product composed of a feature A. Equinox p2 self-update is enabled in the product with a
default Update Site containing new versions of feature A. After exporting the product, my problem is
that the newer versions of feature A on the update site are not detected from the product menu
Help->Check For Updates

However, if in the product I reinstall feature A from the product menu Help->Install New Software...
then, after reinstallation, updates of feature A are detected and correctly installed from
Help->Check For Updates.

So, do I need to modify p2.inf or the product such that p2 is looking for updates of the feature A
by default?

Thanks,

Edmon

PS: I followed the instructions from
http://wiki.eclipse.org/Equinox/p2/Adding_Self-Update_to_an_ RCP_Application

Re: RCP self update [message #533108 is a reply to message #533054]

Wed, 12 May 2010 05:31

Eclipse User

Hi,
I have exactly the same problem ! The only way I can get feature A to be found by 'Check for Updates' is if the product version is also incremented, and you replace the 'old' feature A with the updated feature 'A' in the product dependencies. Then do a product export to your repository. Now if you click 'Check for Updates' it finds the new product version with the updated feature A.
Obviously this is not ideal - ideally feature A can be updated independently of the rest of the product.

One possibility I'm exploring is that the problem is that the product has fixed feature versions, maybe it is possible to specify a range of feature versions.

Re: RCP self update [message #533169 is a reply to message #533054]

Wed, 12 May 2010 09:22

Eclipse User

Also see Richard's thread, but I think
http://aniefer.blogspot.com/2009/07/composing-and-updating-c ustom-eclipse.html
provides the information you need.

PW

--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse .platform.doc.isv/guide/workbench.htm

Re: RCP self update [message #533291 is a reply to message #533169]

Wed, 12 May 2010 23:36

Eclipse User

Originally posted by: edmon70.gmail.com

Thank you very much for your answers and your help.

I tried to figure out from aniefer.blogspot.com the steps required to solve my problem. So, the
first thing I did was to change my p2.inf to add the following lines:
requires.1.namespace = org.eclipse.equinox.p2.iu
requires.1.name = featureA.feature.group
requires.1.range = [1.0.0, 1.2.0)

The good thing about these lines is that it defines feature A as part of the product without being a
requirement (which allow them to updatable/reinstallable) but new versions of my feature are still
not detected.

Note that I forgot to mention that only the qualifier in the version number of feature A is modified.

I also tried to include customAssembly.xml in the plugin of the product (same place than the p2.inf)
but it does not seem to change anything (at least when the product is build/exported from the
product overview).

So, my question now is: since I am not using headless build, how do I customize the build to do the
additional director calls such that feature A is at the root in the installation details (so p2
would look for updates).

Thank you,

Ed

Paul Webster wrote:
> Also see Richard's thread, but I think
> http://aniefer.blogspot.com/2009/07/composing-and-updating-c ustom-eclipse.html
> provides the information you need.
>
> PW
>

Re: RCP self update [message #533335 is a reply to message #533291]

Thu, 13 May 2010 08:27

Eclipse User

Check out the e4 customTargets.xml [1]. Basically you would add an
extra step in your postBuild target to run the director, before you zip
up your product. See my targets run.director and provision.e4.

We also use this in our automated tests [2]. Unzip an SDK and then
install the tests from a p2 repo using the director. See the
installTestPlugins target.

There is a p2 director ant task, but it installs into the running system
(in my build case, that's the basebuilder and it doesn't help me :-)

[1]
http://dev.eclipse.org/viewcvs/index.cgi/e4/releng/org.eclip se.e4.builder/builder/general/customTargets.xml?view=co& content-type=text%2Fplain

[2]
http://dev.eclipse.org/viewcvs/index.cgi/e4/releng/org.eclip se.e4.builder/builder/general/tests/test.xml?view=co&con tent-type=text%2Fplain

--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse .platform.doc.isv/guide/workbench.htm

Previous Topic:	Newbie question: can one RCPize an existing plug-in?
Next Topic:	RCP examples

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 08 00:57:13 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter