1.3 build

[Mark Womack <mw...@apache.org>]

Hi all,

I obviously haven't done the next build for v1.3.  I am trying to get some 
changes together for the FileWatchdog.  I am just rewriting it to be much 
simpler.  I have the changes ready to go, so after we fix the current 
compile errors I will test and check in.

I also think we should replace the Scheduler class with the jdk 1.3 Timer 
class.  Since appears that we will be migrating log4j to at least jdk 1.3, 
it makes sense to not re-invent the wheel.  Any opinions?

-Mark 



---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

Re: 1.3 build

[Ceki Gülcü <ce...@qos.ch>]

If my memory serves me correctly, the Scheduler was written to ensure JDK 
1.2 compatibility. However, it also became apparent that the Scheduler 
offered significant advantages over the JFK 1.3 Timer class. Unfortunately, 
I can't exactly remember what those advantages were but maybe it was the 
methods to find scheduled jobs and to reschedule them with different 
parameters.

At 07:31 AM 4/5/2006, Mark Womack wrote:
>Hi all,
>
>I obviously haven't done the next build for v1.3.  I am trying to get some 
>changes together for the FileWatchdog.  I am just rewriting it to be much 
>simpler.  I have the changes ready to go, so after we fix the current 
>compile errors I will test and check in.
>
>I also think we should replace the Scheduler class with the jdk 1.3 Timer 
>class.  Since appears that we will be migrating log4j to at least jdk 1.3, 
>it makes sense to not re-invent the wheel.  Any opinions?
>
>-Mark

-- 
Ceki Gülcü

    The complete log4j manual: http://www.qos.ch/log4j/


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org