gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <>
Subject Re: Fwd: failure notice
Date Tue, 30 Nov 2004 13:32:42 GMT
At 03:39 AM 11/30/2004, Geir Magnusson Jr wrote:
>some lists choose to moderate...

Hello Geir,

We currently don't but may switch back to moderated list. Sorry about the 

>anyway, the interesting thing is the problem I have fixing Velocity so 
>Gump is happy ...

Niclas Hedhman informed us of this problem. There was a conscious choice to 
remove the old RollingAppender and replace with something better.

To help you solve this problem there several routes exists. First and more 
philosophically, there is more to software development than keeping gump 
happy. Having said that, you can keep gump happy by either switching to 
FileAppender or keep your own version of RollingFileAppender.

Perhaps the easiest alternative is to have velocity explicitly tell gump 
that velocity depends on log4j 1.2.x and not log4j head. Actually this 
would  be he action I would recommended.

I hope this helps,

>Begin forwarded message:
>>Date: November 29, 2004 9:29:02 PM EST
>>Subject: failure notice
>>Hi. This is the qmail-send program at
>>I'm afraid I wasn't able to deliver your message to the following addresses.
>>This is a permanent error; I've given up. Sorry it didn't work out.
>>Sorry, only subscribers may post. If you are a subscriber, please forward 
>>this message to to get your new 
>>address included (#5.7.2)
>>--- Below this line is a copy of the message.
>>Return-Path: <>
>>Received: (qmail 13066 invoked by uid 99); 30 Nov 2004 02:29:02 -0000
>>X-ASF-Spam-Status: No, hits=0.0 required=10.0
>>         tests=
>>Received-SPF: pass ( local policy)
>>Received: from (HELO 
>> (
>>   by (qpsmtpd/0.28) with SMTP; Mon, 29 Nov 2004 18:29:02 -0800
>>Received: (qmail 11965 invoked from network); 30 Nov 2004 02:29:00 -0000
>>Received: from (HELO ? 
>>   by with SMTP; 30 Nov 2004 
>> 02:29:00 -0000
>>In-Reply-To: <>
>>References: <> 
>><> <>
>>Mime-Version: 1.0 (Apple Message framework v619)
>>Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
>>Message-Id: <>
>>Content-Transfer-Encoding: quoted-printable
>>Cc: Gump code and data <>,
>>  Log4J Developers List <>
>>From: Geir Magnusson Jr <>
>>Subject: Re: Gump reporting
>>Date: Mon, 29 Nov 2004 21:28:57 -0500
>>To: Velocity Developers List <>
>>X-Mailer: Apple Mail (2.619)
>>X-Virus-Checked: Checked
>>Why isn't this backwards compatible?
>>I'm trying to fix this, but I can't.  There is no released version of =20=
>>log4j that has this change, and I won't have vel based on whatever we =20=
>>can build from head-du-jour.
>>Is there a way to make this backwards compatible?  Like deprecate =20
>>o.a.l.RFA, release so we can switch to o.a.l.rolling.RFA?
>>On Nov 28, 2004, at 2:38 PM, Paulo Gaspar wrote:
>>>But how do you constrain the use of disk space with the FileAppender?
>>>With the RollingFileAppender, that is a simple matter of =
>>>Paulo Gaspar
>>>Ceki G=FClc=FC wrote:
>>>>Hi Niclas,
>>>>The change is not not a backward compatible. My suggestion would be =20=
>>>>use a simple FileAppender instead of RollingFileAppender.
>>>>At 02:13 PM 11/26/2004, Niclas Hedhman wrote:
>>>>>Jakarta Velocity is somehow using the RollingFileAppender in code, =20=
>>>>>and I
>>>>>wonder if you guys have moved it from
>>>>>     org.apache.log4j.RollingFileAppender
>>>>>     org.apache.log4j.rolling.RollingFileAppender
>>>>>and whether this constitutes a compatible change or not, as I think =20=
>>>>>if this is
>>>>>the case, it will also break a lot of configuration files out there.
>>>>>Thanks for any feedback.

Ceki Gülcü

  The complete log4j manual:
  Professional log4j support:  

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message