Why isn't this backwards compatible?
I'm trying to fix this, but I can't. There is no released version of log4j that has this change, and I won't have vel based on whatever we can build from head-du-jour.
Is there a way to make this backwards compatible? Like deprecate o.a.l.RFA, release so we can switch to o.a.l.rolling.RFA?
geir
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 configuration.
Regards, Paulo Gaspar
Ceki G�lc� wrote:
Hi Niclas,
The change is not not a backward compatible. My suggestion would be use a simple FileAppender instead of RollingFileAppender.
At 02:13 PM 11/26/2004, Niclas Hedhman wrote:
Hi,
http://brutus.apache.org/gump/public/jakarta-velocity/jakarta- velocity/gump_work/build_jakarta-velocity_jakarta-velocity.html
Jakarta Velocity is somehow using the RollingFileAppender in code, and I
wonder if you guys have moved it from
org.apache.log4j.RollingFileAppender to org.apache.log4j.rolling.RollingFileAppender
and whether this constitutes a compatible change or not, as I think if this is
the case, it will also break a lot of configuration files out there.
Thanks for any feedback.
Cheers Niclas
--
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Geir Magnusson Jr +1-203-665-6437 [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
