Hi Rob, Can you add the following to the newsletter?
log4j ----- Here are some salient log4j-related news: - The main branch of the CVS repository is now in quasi-sync with the 1.2 branch [1]. Work on log4j version 1.3 has begun in earnest. - The committers have voted to require JDK 1.2 and drop support for JDK 1.1. [2] - The DOMConfigurator is now able to parse configuration files that contains component specific elements [3]. This significantly improves on existing capabilities. Many thanks to James Strachan for enhacing jelly to deal with dynamic properties [4]. The idea to use jelly in log4j has been shelved for the moment. [5] - Chris Nokes [6] has proposed significant architectural changes to improve memory usage. [1] http://marc.theaimsgroup.com/?l=log4j-dev&m=103420386032223&w=2 [2] http://marc.theaimsgroup.com/?l=log4j-dev&m=103366188809758&w=2 [3] http://marc.theaimsgroup.com/?l=log4j-dev&m=103477613024786&w=2 [4] http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=103479230214745&w=2 [5] http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=103479543318721&w=2 [6] http://marc.theaimsgroup.com/?t=103471060500008&r=1&w=2 -- Ceki TCP implementations will follow a general principle of robustness: be conservative in what you do, be liberal in what you accept from others. -- Jon Postel, RFC 793 -- To unsubscribe, e-mail: <mailto:log4j-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:log4j-dev-help@;jakarta.apache.org>
