> Velocity has been compiling clean in this manner for quite some
> time, which
> by the way is a fact. One that anybody can check. You could have checked
> it. If it were a priority to you.
Sam,
I am not so deeply involved with Jakarta that I go after how GUMP works.
Which does not mean I do not value GUMP. Even not knowing it so well, its
usefulness is obvious just from reading the mailing lists.
I am using Java and Apache stuff for only one year and Apache is already a
quite big "universe" of projects. I use a lot of time to study this stuff,
but I also have to get my work "out of the door" now.
Which means, I am still new on the block, only made few contributions and
am not deeply enough involved to directly deal with GUMP. There is still
a lot to learn before I get to that.
I thought that each project customized its own GUMP "configuration" and
that the behavior you just described was optional.
Anyway, you are right and I am SORRY about this mess. I was now able to
compile with LogKit 1.0 beta 3.
It had failed (repeatedly) quite _less_ than 2 months ago. Maybe Jon is
right and something went wrong with my CVS updates before. I might got
it right when I checked out everything after the recent CVS server
changes.
The kind of input you just gave me made me understand I should be
wrong.
I sure would like (for completely selfish reasons) that Jon would use
his (abundant) energy and knowledge in a more constructive way giving
this kind of input. Things like:
> >> Show me the Gump logs that proves it was more recent than 2
months ago.
do not add anything to what I know and do not help on understanding
when and why I am wrong.
Thanks a lot,
Paulo Gaspar
> -----Original Message-----
> From: Sam Ruby [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 01, 2001 2:27 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [GUMP] Build Failure - Velocity
>
>
> Paulo Gaspar wrote:
> >
> >> Show me the Gump logs that proves it was more recent than 2 months ago.
> >
> >Jon, the facts are:
> > - The LogKit jar (log.jar) that I got from CVS a couple of days
> > includes classes compiled on May 5th, 2001;
> > - All the 3 LogKit betas were released after that. Check
> > http://jakarta.apache.org/avalon/logkit/changes.html ;
> > - Velocity does not compile with (at least) the last 2 of them.
> >
> >These are the facts. Anyone can check them. You could have checked
> >them.
> >
> >I do not have the faintest idea about what Gump does and it is not
> >one of my priorities to know it.
>
> What Gump does is ignore the jar which is compiled in CVS and
> compiles each
> project (Velocity in this case) with against the jars produced by
> compiling
> the latest version (from CVS) of each dependency (e.g. Logkit). Daily.
>
> Velocity has been compiling clean in this manner for quite some
> time, which
> by the way is a fact. One that anybody can check. You could have checked
> it. If it were a priority to you.
>
> - Sam Ruby
>
