[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[p2-dev] ant tasks needed to drive e4 builds
- From: Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 24 Jun 2009 16:20:07 -0400
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; b=DnE0Dz3xHxwrj+0qI/hphbqJSUcxQU88aELtlb6GrtXCudSJH2l+V3TkIZQ9Xuvtwe 5MXtjEvjbHCL93nZFpwNcKMly0fjvVQtpSaIHlHIl3H5RR0uWCEpVrdODXCjN/J6xD25 qfWC5e7g6OMWGVUUoblMvcPPzzGxU+FTCKARc=
I'd like to solicit help with the e4 builds.
Right now org.eclipse.e4.builder/scripts/masterBuild.sh launches the
e4 builds. It uses org.eclipse.e4.builder/builder/general as the
builder (we build against a master feature, org.eclipse.e4.master) and
copies/modifies templates from org.eclipse.e4.builder/templates to
generate the published download site.
But a number of artifacts are generated by the script, the tests are
run from the script, the difference between test builds and published
builds are controlled by the scripts, etc. That makes this very much
a linux only build. Plus, it also must consume 4 zipped repos (using
repo2runnable) that must be provided, for example:
I'd like help to convert most of what the bash script does to an ant
driven build. The goal would be that a test build could be launched
from within eclipse on any of the platforms.
If anyone can help please join in the discussion (or with patches! :-)
Hi floor. Make me a sammich! - GIR