[ http://issues.apache.org/jira/browse/VELOCITY-403?page=comments#action_12330730 ]
Nathan Bubna commented on VELOCITY-403: --------------------------------------- At Tim Colson's wise behest, i'm adding these comments (previously sent to the dev-list): despite the scope of the changes, most apps currently using Velocity probably won't notice any difference, except perhaps the addition and use of StandardOutLogSystem and JdkLogSystem. any developers who have implemented their own LogSystem's will have to add two simple methods to their implementations if they decide upgrade to 1.5. this is likely to be uncommon, very easy to do, and won't make their library incompatible with earlier Velocity versions. VelocityTools falls into this category. also, any developers who implement their own Uberspect, don't extend UberspectImpl, and implement UberspectLoggable (read: no one) will have to implement one new method in the UberspectLoggable interface, which again, won't make them incompatible with earlier versions of Velocity. in other words, the changes are backwards compatible, and the deprecation path is clearly set. there's no reason to wait for 2.0 before adding these enhancements. > 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 > Attachments: logging.patch > > 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]
