The desired goal is to release log4j 1.3alpha0 sometime this month.
Here is the current state if affairs from my viewpoint.
1) Joran is not yet complete even if very significant progress has been made recently.
2) PatternLayout needs support from Joran to learn new patterns on the fly. Joran should support PatternLayout's requirements within the next few days.
3) The internals of log4j are not yet stable. In log4j 1.3, log4j will use itself for its own logging, which means that there must a clear separation between log4j's internal logging space and the rest. We do not have that yet. This will be solved by log4j domains. Domains do not require much code. A better description of the problem will follow once 1 and 2 are completed.
4) Log4j needs to deliver management events to support various listeners and management operations.
5) Log4j should be manageable by JMX.
Points 4 and 5 can wait until after log4j 1.3alpha.
What else do you have in mind?
At 08:48 AM 9/17/2003 +1000, you wrote:
Do you think we should openly discuss a plan for a Log4j 1.3 Alpha release on the dev list? Personally I deal better when a target date is there in front of me, together with a target agreed set of functionality to complete.
cheers,
Paul Smith
-- Ceki Gülcü
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp import org.apache.Facetime;
ApacheCon US 2003, 18-21 November http://apachecon.com/--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
