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 2005/10/03 09:07:47 UTC
[jira] Commented: (VELOCITY-166) avoid setting up file logging
[ http://issues.apache.org/jira/browse/VELOCITY-166?page=comments#action_12331136 ]
Will Glass-Husain commented on VELOCITY-166:
--------------------------------------------
I think this was resolved by VELOCITY-403 (scheduled for version 1.5). Nathan, do you agree?
> avoid setting up file logging
> -----------------------------
>
> Key: VELOCITY-166
> URL: http://issues.apache.org/jira/browse/VELOCITY-166
> Project: Velocity
> Type: Improvement
> Components: Source
> Versions: 1.3.1
> Environment: Operating System: All
> Platform: All
> Reporter: Jens Elkner
> Priority: Minor
> Fix For: 1.6
>
> Please avoid trying to setup file logging, if RuntimeConstants.RUNTIME_LOG
> property is not set or empty. The thrown exception (e.g. in
> SimpleLog4JLogSystem#init) is misleading! Having no [file] logging
> set, AFAIK has no implications on the production of the results,
> so it is neither a PANIC situation nor worth for a warning message.
> I would at max. assign it to the INFO level, speaking in terms of a log system...
--
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