> I thing, the problem is in the product build, and not in the p2 installation?
That’s what I’m trying to figure out J
To summarize (correct me if I’m wrong) - the issue is that executable files of your product are missing after its installation.
I assume they are packed in the only binary artifact you have (myproduct.product.rootfiles.win32.win32.x86_6.3 for Indigo)
On one hand binary IU is presented in the p2 profile which means it’s successfully installed from p2 point of view, on the other - the physical artifacts are missing.
I have two guesses what could have gone wrong:
- Product build hasn’t includes the executables in the binary for some reason - You can check whether in binary folder of your generated p2 repo whether myproduct.product.rootfiles.win32.win32.x86_6.3 archive contains all files you expect to have in your installation.
- p2 installation :
o there has been no action found corresponding to the binary touchpoint instruction (in your case unzip action) or
o action execution has failed
this would be trickier to be checked so let’s start with the first one.
p2 folder is a working folder so I don’t think differences in it are relevant but could be wrong.
One comment on the IDs of your product – when you say “myproduct.ide”, do you mean the exact ID of the product or it’s just abbreviation?
I’m asking because the content.xml you attached doesn’t contain neither myproduct.ide nor myproduct.product and looking at different repositories could be misleading.
HTH
Katya
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Boian Tomov
Sent: jeudi 21 juillet 2011 12:48
To: P2 developer discussions
Subject: Re: [p2-dev] Installing a Eclipse based product
I'm not sure if this is realy a problem, but i have compared the generated with ganymede repository and with indigo and found, that there are different.
My binary generated with
ganymede is: myproduct.ide.launcher.win32.win32.x86_6.3 and with
indigo: myproduct.product.rootfiles.win32.win32.x86_6.3
I thing, the binary should be myproduct.ide, because the build.properties file is the same, and the id of the product is myproduct.ide.
And so, when i can try to install the product with the indigo p2.director the ID myproduct.ide can't be found, and a simple look in -list options shows that the product has the the id myproduct.product. Installing with myproduct.product works fine, but there are differences in the p2 folder. The folders org.eclipse.equinox.p2.director and org.eclipse.equinox.p2.metadata.repository are missing.
I thing, the problem is in the product build, and not in the p2 installation?
What can be different?
Thanks,
Boian
I have a few more questions (just to check whether my observations are in the right direction):
- Executable file that your installation lacks are packed in the binary com.seeburger.devstudio.product.rootfiles.win32.win32.x86, right?
- Could you check the value of the 'org.eclipse.equinox.p2.installFolder' property in your oldest p2 profile? (I'm curious if the values differ between the oldest and the newest profile)
-----Original Message-----
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Boian Tomov
Sent: mercredi 20 juillet 2011 12:37
To: P2 developer discussions
Subject: Re: [p2-dev] Installing a Eclipse based product
Here are the content.xml and the p2 profile.
Thanks in advantage,
Boian
Could you please attach the content.xml of your generated repository and the last p2 profile of your installation?
You can find the profile under:
<location of the new created product>/p2/org.eclipse.equinox.p2.engine/profileRegistry/MyEclipseProduct/<the most recently created file>
Thanks,
Katya
-----Original Message-----
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Boian Tomov
Sent: mercredi 20 juillet 2011 11:00
To: P2 developer discussions
Subject: Re: [p2-dev] Installing a Eclipse based product
So, i have changed the productID to myProduct.feature.feature.group and
the installation works fine, but without any executables. Run the p2
director with productID: myProduct.product copy the binaries to the
destination folder, and i can start my product. But the problem now is
that my product is not p2 enabled and when i copy additional plugins to
the dropins folder, my product couldn't find it.
The links don't seem to refer to anything related to creating installs.
Could you please double check?
On 2011-07-19, at 11:16 AM, Boian Tomov wrote:
Hi,
i'm try to migrate my current eclipse product from ganymede (3.4) to Indigo.
The problem is, when i run the p2 installer (described in http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.jdt.doc.isv%2Fguide%2Fjdt_apt_building_with_apt.htm - Installing a complete product ),
the p2 director ends very short successfully and the result folder contains only the p2 folder, the plugins folder and artifacts.xml.
I shorter look in the result, showed that the product executable file, the features folder are missing.
The installation repository contains all needed plugins and features, and was build such in the documentation (http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.jdt.doc.isv%2Fguide%2Fjdt_apt_building_with_apt.htm)
The same scenario has worked fine in Ganymede, but no more in indigo. Maybe i miss some steps?
Thank you in advantage.
Regards,
Boian
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
