[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: Fw: [p2-dev] Failed to run the product build

If you are running product builds (productBuild.xml) and you want the launchers then  you
1. must set your config specs to include the platforms you want to bulid for (win32, win32, x86 for example).
2. Ensure that the delta pack (or at least the exe feature and launcher fragments) are on your pluinPath

I usually just point pluginPath to the root of the delta pack.

For reasons that Andrew can explain, you can't put the delta pack in the dropins (or on any update site).

cheers,
ian

On Sun, Jun 13, 2010 at 7:51 AM, Samuel Wu <samuelwu@xxxxxxxxxx> wrote:

Thank you, Andrew, for the suggestion. It works find for exporting the product from the Eclipse GUI but doesn't work for the headless build.
1. The first thing I tried was to unzip eclipse-3.6RC3-delta-pack.zip in the eclipse dropins directory and update the pluginpath in build.properties file topluginPath=D:/eclipse-SDK-3.6RC3/eclipse/dropins/eclipse,
The product export works fine but headless build doesn't include plugin.exe
2. I then tried to build an update site to include feature org.eclipse.equinox.executable and install the feature into Eclipse. I got the same result.
3. I manually copied feature org.eclipse.equinox.executable to the features folder, somehow the feature installation didn't create the folder. It still doesn't work for the headless build.
Anything else I can check? Thanks.

Best Regards

Samuel Wu

----- Forwarded by Samuel Wu/Toronto/IBM on 06/13/2010 10:43 AM -----


From:

Andrew Niefer/Ottawa/IBM

To:

Samuel Wu/Toronto/IBM@IBMCA

Date:

06/10/2010 10:50 AM

Subject:

Re: Fw: [p2-dev] Failed to run the product build



There is a setting on the overview tab of the .product editor "The product includes native launcher artifacts". Make sure this is selected.

Also, in a headless build you will need the org.eclipse.equinox.executable feature to be present. This feature is part of the deltapack:
http://download.eclipse.org/eclipse/downloads/drops/S-3.6RC4-201006031500/download.php?dropFile=eclipse-3.6RC4-delta-pack.zip
When using the deltapack make sure you get the version from the same build as the rest of your target.

In a headless build you can extract the deltapack to some directory and use the "pluginPath" property to point to the eclipse folder from it.


For the version thing you before, I tried to explain earlier. The releng build uses map files that specify a specific tag to get from cvs:
plugin@xxxxxxxxxxxxxxxxxxxxxxxxxxxx=v20100503,:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/rt,,.....
The build checks out that specific "v20100503" version from cvs, it does not get the latest from head.
Each week, the developers tag their code in cvs with a new version then update the map file to refer to the new tag. If they don't update the map file with a new version, then the old version keeps getting used.

-Andrew




From:

Samuel Wu/Toronto/IBM@IBMCA

To:

p2-dev@xxxxxxxxxxx

Date:

06/09/2010 09:35 PM

Subject:

[p2-dev] Failed to run the product build

Sent by:

p2-dev-bounces@xxxxxxxxxxx




This is a test with Eclipse 3.6 RC3. I have a product build which has a feature which includes Eclipse platform. I also have a headless build for the product. After the product build, I found that eclipse.exe was not included in the package generated. So I added it manually. When I tried to run it, I got the error message "The Eclipse executable launcher was unable to locate its companion library. Can you please shed some light?

Best Regards

Samuel Wu
_______________________________________________
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




--
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource

GIF image