> -----Original Message-----
> From: Felipe Leme [mailto:[EMAIL PROTECTED]
> Sent: lundi 8 août 2005 02:30
> To: Cactus Developers List
> Subject: Re: [EMAIL PROTECTED]: Project jakarta-cactus-sample-servlet-13 (in
> module jakarta-cactus) failed
> 
> Hi all,
> 
> First of all, sorry for being away in the last weeks, but I moved
> recently and wasn't totally online yet...
> 
> So, is Gump broken because of the Cargo dependency? If so, how should we
> fix it? More specifically, is it caused by that hack of hardcodinng
> Cargo version to 0.5? If it's not that, it might be an error on the Gump
> configuration...

The only thing I know is that the Gump failure is not a real failure and
that's the issue I have with Gump: 99% of the time it reports false alarms
and 99% of the time is spent in fixing it. It's really a great tool if you
have the time to follow it but as soon as you drift a bit away from the
project, it's cost is too high IMO.

I have stopped caring about Gump a few years ago. I used to love it when I
was 100% on Cactus and I was happy maintaining it. Now, I don't have the
time anymore.

I think we should ask to remove the email nags unless some Cactus committers
wants to maintain it.

Felipe, would you like to maintain it?

It's probably missing the Cargo dependency that needs to be added. The Gump
project files are located in the Gump project itself in
project/jakarta-cactus.xml. I'm sure you can easily get CVS commit rights if
you say that you want to maintain the Cactus GOM.

Thanks
-Vincent


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to