You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Will Glass-Husain (JIRA)" <ji...@apache.org> on 2006/11/06 06:41:39 UTC

[jira] Commented: (VELOCITY-392) Switch to a better log system - slf4j

    [ http://issues.apache.org/jira/browse/VELOCITY-392?page=comments#action_12447367 ] 
            
Will Glass-Husain commented on VELOCITY-392:
--------------------------------------------

Makes sense.

Obviously, you could always create a LogChute that acts as a bridge between Velocity and slf4j.

> Switch to a better log system - slf4j
> -------------------------------------
>
>                 Key: VELOCITY-392
>                 URL: http://issues.apache.org/jira/browse/VELOCITY-392
>             Project: Velocity
>          Issue Type: Improvement
>          Components: Engine
>    Affects Versions: 1.5
>         Environment: Operating System: All
> Platform: All
>            Reporter: Jens Elkner
>         Assigned To: Henning Schmiedehausen
>            Priority: Minor
>         Attachments: velocity.patch
>
>
> Since I'm still very unhappy with the current logging workaround in velocity, I
> removed the complete velocity logsystem stuff and replaced it with slf4j (see
> http://slf4j.org/manual.html ; http://slf4j.org/faq.html). So, the final thing
> is a little bit smaller and should be wrt. logging easier to use (i.e. no need
> for passing runtime svc handles back and forth just to be able to log
> something), much faster, safer and more precise and powerful than the old one...
> In case your are interested, I'll attach the patch made against the saturday
> evening svn repository. It basically contains the log changes as well as some
> code cleaning (i.e. remove/comment out unsed vars/methods, removed unneccessary
> casts as well as nested else clauses, removed throw XExceptions, which are
> actually not thrown). Finally I switched many log.info into log.debug, since the
> appropriate messages are important for developers only and should not irritate
> the enduser (who usually doesn't even understand that freak language ;-)).
> To get the thing running out of the box, I modified the buildfile to include
> log4j.properties in the jar, so that nlog4j aka log4j NG ;-) finds and uses it
> automatically, if one has not explictly configured it. And of course
> build/lib/log4j has been replaced with nlog4j (see
> http://www.slf4j.org/nlog4j/download.html)
> Regards,
> jens.

-- 
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: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org