|
|
| Re: Generate update site during headless build? [message #667677 is a reply to message #667662] |
Sun, 01 May 2011 08:15   |
 Volker Wegert
Messages: 182
Registered: July 2009 |
Senior Member |
|
|
Am 30.04.11 21:16, schrieb Trip Gilman:
> Are you using a build server like hudson, or are you doing this
> manually?
Manually automatically - that is, a cronjob starts a shell script that
starts java that starts the antRunner.
> Could you describe your current build process?
It's more or less "the standard PDE build". The main differences are
- I'm fetching from svn instead of CVS
- I'm not fetching the map file from CVS but copy it in place in an
ant task
- I use p2.mirror to build a local repository of the other packages
required by and included in my product (although that's in a separate
cron job)
- I'm building for Linux, MacOS, and Win32 with 32 bit and 64 bit
each, so the build generates six "usable" zip files and a seventh one
that I ignore.
In the previous build system (based on 3.3), I had to run the entire
build twice - once with outputUpdateJars set to false (that created the
distributable zip files) and once with outputUpdateJars set to true
(that created crippled zip files but a usable basis to draw the contents
of the update site from). Now with p2, I hope there's a better way to do
this. I assume one of the ant tasks is able to push the compiled
packages into an update site, but which one is it?
Thanks
Volker
--
* Volker Wegert * http://www.volker-wegert.de/contact *
|
|
|
|
Powered by
FUDForum. Page generated in 0.03815 seconds