We currently have something that is simple and that works. While I can clearly see the disadvantages of switching to a new tool, I fail to see any obvious advantages of mavenizing log4j. What is in Maven that we need and do not currently have?
At 09:07 AM 7/7/2003 -0400, you wrote:
Paul Smith wrote:
I think it's an excellent idea, perhaps we could develop a Maven build on the side for those who wish to use it, and if everyone's happy we could perhaps vote to switch to it for good. Maven's reports are excellent additional information for the log4j web site too.
This is the approach that Avalon did. It works well. What we did was to create a profile in GUMP and a minimal build.xml file so that GUMP would continue to work.
Take a look at the avalon-logkit for an example of how things were done in place.
--
Ceki For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
