[ http://issues.apache.org/jira/browse/VELOCITY-403?page=comments#action_12329899 ]
Henning Schmiedehausen commented on VELOCITY-403: ------------------------------------------------- I do know that Geir is very hesitant to consider commons-logging. I can follow his reasoning to some point. However, if we start to rebuild the whole mess with logging detection, JDK 14, log4j, logkit switch and so on, we will end up with a commons-logging Frankenstein inside the velocity jar. Which I'd really want to avoid. For Velocity 1.x, we're pretty much stuck with what we have. For 2.x, I'd love to see that we at least consider whether c-l would be an option. We over there at turbine land never ever regretted the switch from the old, 2.1 self rolled logging system which was only usable in the default configuration and you couldn't touch it to "commons-logging everywhere" with a strong leaning towards log4j. The whole discussion about log improving leads that we either use some sort of logging bridge (and unfortunately Ceki has chosen to play ideology instead of pragmatism with his "UGLI" attempt (which seems to went AWOL these days)) or just commit to a single logging system (which probably would be log4j these days). > Enhance Velocity's LogSystem and internal use thereof > ----------------------------------------------------- > > Key: VELOCITY-403 > URL: http://issues.apache.org/jira/browse/VELOCITY-403 > Project: Velocity > Type: Improvement > Components: Source > Reporter: Nathan Bubna > Fix For: 1.5 > > After several very, very long debates with Geir over commons-logging, i have > become largely convinced that it is something we should do with hesitation > (i.e. let's talk about it for 2.0, but not before). i've also begun to have > some frustrations with commons-logging in both work projects and in > VelocityTools. > regardless of these issues, it is clear to me that Velocity's LogSystem and > use of it is in great need of improvement. we need to lower the priority of > many messages, eliminate some, and above all, upgrade the system itself to be > more useful. > some specific, unevaluated, off-the-cuff ideas are: > -make logging a null-op if no logger is found, rather than panic and break > -detect jdk 1.4+ logging > -add a trace level > -add is<Level>Enabled > -make it possible to grab a LogSystem instance of sorts, so Velocity > extensions can use it more sensibly (i'm tired of the hacks we must do in > Tools) > those are just a few ideas, and they might not all even be feasible. still, > i'm hoping to take a whack at some of this and hoping that others can help me > out. my volunteer time is still rather limited. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
