RCP self update [message #533054] |
Wed, 12 May 2010 06: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 #533291 is a reply to message #533169] |
Thu, 13 May 2010 03: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
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03832 seconds