Comments on: RCP Self Provisioning with P2: It Works!!!

By: Andrey

Andrey — Mon, 14 Dec 2009 13:57:25 +0000

Oups, after 1 hour of building it is ended with an “Out of memory” error.

By: Andrey

Andrey — Mon, 14 Dec 2009 13:56:14 +0000

Thanks for very valuable tutorial.
Some important thing for improvement.
Please note that in

>-installIU p2_maildemo.product

This should be the product ID and not a path to a *.product file. I spent half a day to figure this out.

For example if in you *.product file you use the following id My_definition.My_tool

The option should look like:
-installIU My_definition.My_tool

Another thing that is frustrating is that building/installation of RCP takes hours. Probably it is only in my case. Something happens. I don’t know if it is Ok, since the only sign that is not finished is that the Windows Task Manager shows heavy CPU load.

By: Joe

Joe — Tue, 11 Aug 2009 13:33:41 +0000

I am having so much problems trying to add self-updating to my RCP App. Could you please provide the source of the latest rcp mail demo that has p2 updating working? It would be greatly appreciated. Thanks so much!

By: Kai Tödter

Kai Tödter — Sun, 26 Jul 2009 06:00:30 +0000

So much changed with 3.5. I currently port all the p2 and build stuff of my mp3m to 3.5. I works now, but I have to figure out some strange things. As soon as I am done I will blog about it.

By: Carsten Nikiel

Carsten Nikiel — Fri, 17 Jul 2009 11:22:24 +0000

@Kai for point 11 you might be able to use a p2.inf file at the same level as the .product file with this content:
instructions.configure=\
addRepository(type:0,location:PATH-TO-REPOSITORY);\
addRepository(type:1,location:PATH-TO-REPOSITORY);

Since I am using eclipse 3.5 too to get this to work I face the very same issues and questions that Vincenzo Caselli has.

By: Vincenzo Caselli

Vincenzo Caselli — Tue, 23 Jun 2009 18:08:19 +0000

More doubts:
* we are following your tutorial with Eclipse 3.5 and when using the director app we discarded the “version” option (not allowed), is it right or is there an equivalent option?
* we are using the option “-application org.eclipse.equinox.p2.director” instead of “application org.eclipse.equinox.p2.director.app.application” since the latter is warned as deprecated in the console
* at point 10 you say “Exported the new product version 1.0.1 in the SAME location, to update the metadata/artifact repositories.”: we are supposing we have to remove folders “eclipse” and “repository” each time before the Export, since if we do not do this we are receiving a conflict version error. Is this right?
* we are supposing the director app is to be launched just the first time, to create the initial setup. Only the Export has to be performed at each update phase. Right?

Thank you so much Kai.
Vincenzo Caselli

By: Vincenzo Caselli

Vincenzo Caselli — Tue, 23 Jun 2009 17:03:29 +0000

Hi Kai,
at point 11 you say:
“11. So I added the repository c:/java/RCP/p2-maildemo/repository manually as a new site, and voila, the new version 1.0.1 was displayed and ready for update.”
But how did you do this? I do not have any “Add…” button to the right of the “type filter text” text box (like in the IDE), nor any “Window, Preferencies..” to add a new Update Site. We are near to the end, but are missing the last step …
Thank you very much
Vincenzo Caselli
RCP-Vision.com

By: izyl

izyl — Tue, 26 May 2009 09:32:59 +0000

Hello, p2 updates works fine for me.
I can update my product, but i’m wondering how to allow user to install a new plugin.
I can make another site but what if i want to use the same update site so that i can enable automatic update.

Is it possible to automate the update from the begining (first time the product is opened).

As u said, i had to add the site manually through the p2 ui so i can download the new version or use the new update site with the new plugins.

Have you got a clue for me?

By: Jason

Jason — Fri, 03 Apr 2009 16:14:12 +0000

Hi Kai,
Do you encounter the following error when you play with the P2 self update demo project?
An error occurred while collecting items to be installed
session context was:(profile=profile, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Collect, operand=null –> [R]org.eclipse.equinox.p2.examples.rcp.cloud.product_root.win32.win32.x86 1.0.1.200904032238, action=).
The required Touchpoint: org.eclipse.equinox.p2.native 1.0.0 touchpoint for the collect action is not included in the installation manager configuration.
The required Touchpoint: org.eclipse.equinox.p2.native 1.0.0 touchpoint for the collect action is not included in the installation manager configuration.

Here is my steps:
1. Down the source from the eclipse site(org.eclipse.equinox.p2.examples.rcp.cloud and org.eclipse.equinox.p2.examples.rcp.cloud.releng), run –> Build Cloud Example from Build Cloud Example.launch file by right clicking. A builded product is generated by default. It runs;
2. Change the version number from 1.0.0 to 1.0.1 both in cloud.product and plugin.xml files and build again, it runs ok;
3. From 1.0.0 version product click Install new softerware and add the local site I generate the 1.0.1 version location, new version is found. But when I select the new version and click Next –> Finish the exception above occurrs. I have no any idea to sovle the problem. Will you please help me for this?

Thanks a lot in advance.

By: Udo

Udo — Wed, 25 Feb 2009 07:11:48 +0000

The “Cannot launch the Update UI. This installation has not been configured properly for software updates” problem.

I had this some days ago, too, and fixed it by correcting the config.ini file in the application. After that the update dialog appeared again.

I think the properties eclipse.p2.data.area and eclipse.p2.profile are necessary to let the dialog show correctly.