Re: [epp-dev] EPP automated build, first incarnation

[Markus Knauer <mknauer@xxxxxxxxxxxxxxxxx>]

Here are question 2 and 3:

- I started an EPP build with the newly generated repository and the Galileo repo and it seems to end up as an all-in-one package (should be: CPP only package). Is there an error in the dependency generation? If I am doing a product export and generate my p2 repository 'the old way' I don't have this problem.

- Would it be possible (or maybe helpful?) to move the feature dependencies in the feature from 'requires' to 'includes'? We talked about this before.

[My local EPP testbuild finished now as expected without the binary/executable.]

Thanks and regards,
Markus

2009/5/14 Markus Knauer <mknauer@xxxxxxxxxxxxxxxxx>

Thanks, Thomas! That is great. I tried it immediately and had a p2 repository with all EPP bundles and features in just a few minutes! After this success here are the first questions...

It generated the feature/ and plugins/ directory, but when I am exporting the .product manually I also export it for different platforms which results in an additional binary/ directory with the zip's that include the eclipse executable etc. (e.g. binary/epp.package.reporting_root.cocoa.macosx.x86_1.0.0)

In the end the content of those is the same as in the files distributed by the platform team (e.g. org.eclipse.equinox.executable_root.cocoa.macosx.x86_3.3.200.v20090429-1630-7M-Fm-FI3UouOdfuhJyz-z0c).

Are those binaries really necessary or can they be omitted (like you do it in your build)?

More questions will follow soon... building a package right now.

Regards, Markus

2009/5/14 Thomas Hallgren <thomas@xxxxxxx>

Hi,
I just checked in the first version of the EPP automated build. The result of the build is an update site that is intended to be contributed to Galileo.

If you want to try it out, you can follow these steps:

Log in to build.eclipse.org:

bash> cvs -d :pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/org.eclipse checkout -d org.eclipse.epp.allpackages.feature www/buckminster/samples/epp/org.eclipse.epp.allpackages.feature
bash> cd org.eclipse.epp.allpackages.feature
bash> ./eclipse.build.sh

The generated site can be found in ~/epp.build/buildresult/org.eclipse.epp.allpackages.feature_1.0.0-eclipse.feature/site.p2/

I've had some issues with SocketTimeoutExceptions. If you run into that, just run the build again (it won't clean out the result unless you explicitly tell it to). There are solutions to that problem (such as using file URL's instead of http) and I also belive P2 has made some progress since M7 (which this build is based on).

Documentation in the form of a wiki page will follow.

Regards,
Thomas Hallgren
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev

-- 
Markus Knauer
EclipseSource
###   phone: +49 721 664 733 0  (GMT +2)
###     fax: +49 721 664 733 29
###     web: www.eclipsesource.com

Innoopract Informationssysteme GmbH
Stephanienstrasse 20, 76133 Karlsruhe Germany
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883