This is the right mailing list. I've been heads down coding on a various
activities, and others can easily verify that I've not been seen much from
lately, but I need not bore you with this...
Answering your questions.
> On what machine GUMP builds are run ?
These posted builds are done on a 300 Mhz Pentium II runing RedHat 7.1
Linux with Sun JDK 1.3 installed. This machine is currently in the third
floor of my house, connected to the internet via a cable modem. I a few
times a week run the same build on my laptop, and occasionally on two other
machines.
All the code necessary to run the builds yourself is checked into
jakarta-alexandria cvs, in the directory proposal/gump.
Others have run gump...
> Is there any servlet engine (Tomcat 3.x, Tomcat 4.x, ...) installed on
that machine so
> that we could run functional tests as well during the build ?
Installed? No. But built? Absolutely. An attempt is made to build both
Tomcat 3.x and Tomcat 4.x every run.
> In term of GUMP integration, Cactus Ant build scripts have 3 targets
that
> might be interesting :
> - "tests", run all tests on selected servlet engines (selection is done
by
> editing a build.properties file at the same location as build.xml)
At the moment, there is no logic in Gump which would "edit a
build.properties file", but patches are welcome. ;-)
> - "dist", run everything except the tests and packages the distibution
> files. There are 3 output files that would need to be copied to the
>
/www/jakarta.apache.org/builds/jakarta-commons/nightly/commons-cactus/<date
> of build>. Files are : commons-cactus-22-<date>.zip,
> commons-cactus-23-<date>.zip and commons-cactus-src-<date>.zip
I'm getting errors when I try that, but I will debug. If I have any
questions, I'll let you know.
- "all" : does it all : dist + tests
Great - once you take a look at the "tests" target and I'll take a look at
the "dist" target...
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
