You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Nathan Bubna (JIRA)" <ji...@apache.org> on 2005/10/05 19:40:48 UTC

[jira] Resolved: (VELOCITY-166) avoid setting up file logging

     [ http://issues.apache.org/jira/browse/VELOCITY-166?page=all ]
     
Nathan Bubna resolved VELOCITY-166:
-----------------------------------

    Resolution: Fixed

Ok, i've committed the patch i made myself (revs 295046, 295048, 295050, 295051).  This issue is now resolved. :)

> 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.5
>  Attachments: morerobust.logging.patch, second.morerobust.logging.patch
>
> 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