> -----Original Message-----
> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]
> Sent: den 28 februari 2003 15:09
> To: Avalon Developers List
> Subject: Re: [GUMP] Build Failure - excalibur-xmlutil
>
>
>
>
> Berin Loritsch wrote, On 28/02/2003 14.56:
> > However, I do have to say that the *concept* of GUMP
> > is good. The fact that you build your project based on
> > the current CVS of all the dependencies.
The concept is excellent.
> And BTW, Gump does not build, it launches builds. So effectively you
> *do* use the same build tool when using Gump.
Given the vast differences in environment, it isn't the same.
> Actually it is, but not per design ;-)
> The implementation uses XSLT which seems to suck badly as a
> templating
> system. Change to Velocity, and it will get much better.
I'd say that's not the main fault. If Gump worked like it did now,
but with Velocity, it would still be bad.
The problem is that you don't run Gump locally.
Where I work, the very same build system that does nightly
builds run on each developer workstation. Thus, if it builds on
the workstation -> it builds in the nightly build.
Really, why do we have JARS in CVS? We should just have to specify that
the project needs jars A, B and C, and make that version 2.0.3 of C,
please?,
and then the build system should handle the rest - setting up classpaths
and so on.
I don't want to type
ant build
to build. I want
gump build
.
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
