> > I also wonder if you are proposing to donate the code the Apache Logging > > Log4j > > project? Theoretically, it could be yet another Log4j companion project. > > Maybe we could create a "configuration" companion to encompass useful > > configuration code. There could even be code to utilize other more full > > featured configuration projects such as commons-configuration or provide > > Spring Application Context integration. Just a thought.
As to working into commons-configuration and the Spring Application Context system... I initially started off with the idea that I'd like to configure Log4J using Spring, since that's what I use for most environment-specific configs. However, if something goes wrong in Spring, I'd it to tell me what happened using Log4J. So there's a vicious cycle if something goes wrong; Spring depends on Log4J depends on Spring. Ultimately it was simpler and clearer just to make it depend on system properties for now, with the option of expanding it later. Will. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]