You could do what I did... write a custom logger that forwards the messages to Log4J, but filtering out some of the more annoying Velocity log messages. Wasn't very hard.
IMHO, some of the INFO messages are useful, but others would have been better as DEBUG.
I'll do something I only do infrequently, which is to defend Velocity. In general, in terms of logging messages, it is better to err on the side of being overly verbose. To err on the opposite side means being silent about potential problems.
Meanwhile, this really is such a non-issue. Velocity is an open-source project, so you have the code. If you really find that having Velocity log in certain spots is annoying, you can simply comment out the line(s) in the code where the annoying logging occurs and rebuild the jar.
Or, IOW, if one is going to be picky at this level (since the extra logging messages are benign after all) then one should be willing to make some slight effort to address the "problem". When you download open-source code, no guarantee of any sort is being made, that is clear in the text of the license. That said, to make noise about issues which are non-trivial for an end-user to address is right and proper, but this logging business...
Cheers,
Jonathan Revusky
--
lead developer, FreeMarker project, http://freemarker.org/
Velocity->FreeMarker template conversion tool, http://freemarker.org/usCavalry.html
WILL
_______________________________________ Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
