[ http://issues.apache.org/jira/browse/VELOCITY-392?page=all ]
Henning Schmiedehausen resolved VELOCITY-392.
---------------------------------------------
Resolution: Won't Fix
Assignee: Henning Schmiedehausen (was: Velocity-Dev List)
Nope. -1 here. If we move to another logging system it's either JCL (Jakarta
commons logging) or log4j directly.
There is so much mud slinging around the log4j, nlog4j, slf4j and logback
projects (not to talk about the licensing issues with logback to which slf4j is
dangerously near) that I don't want to go near there.
Nathan did a major rework for velocity logging for 1.5 and currently, while the
logging is still a bit too heavy for my liking (I'd like to switch to JCL),
there is no way that we move to a politically encumbered project that is run
outside the ASF for something as mission critical as logging.
> 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: Source
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
