----- Original Message -----
From: "Sam Ruby" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 28, 2001 9:12 PM
Subject: Re: [REPOST] [GUMP] Cactus nightly builds
> 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...
>
Actually that's what I assumed. I have to apologize Sam for my previous post
which was a bit rude ... ! To tell the truth, I wanted to force you to react
... :-)
I know this is really bad. I promise not to do it again !
> 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...
>
Ok, so it really has to go through you I guess. I was just asking in case I
could help you set everything up.
> > 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.
>
Good. So we can make the Cactus build depend on the Tomcat builds and even
run the tests on both servlet engines (that would really be neat !)
> > 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. ;-)
:)
Actually you don't need to use a build.properties file. You can just pass
the mandatory parameters using the -D switch.
>
> > - "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.
>
As an afterthought : one problem that you may have with Tomcat 3.x (it is a
problem that has been reported today) is that the server.xml file that is
used works with Tomcat 3.2 but seems to fail with Tomcat 3.3, meaning that I
have to create a new entry for Tomcat 3.3 (will do that this week end). I
have not tried it with the latest Tomcat 4.x builds but it works with an
old jakarta-tomcat-4.0-b1 (I guess I'll also have to update that this week
end to verify it works with the latest build) ...
Send me the error so I can have a look.
> - "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...
>
You lost me here :)
What do you want me to do with the "tests" target ? Fix the problem you're
having ? No problem, just give me the error messages ;-)
Thanks Sam and sorry for bothering you with this .... but you know, now that
Cactus is getting a little popular, everyone is putting a lot of pressure on
myself for having nightly builds ... :)
> - Sam Ruby
- Vincent Massol
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
