[jira] Closed: (VELOCITY-163) LogManager should use NullLogger as Fallback

["Henning Schmiedehausen (JIRA)" <de...@velocity.apache.org>]

     [ https://issues.apache.org/jira/browse/VELOCITY-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henning Schmiedehausen closed VELOCITY-163.
-------------------------------------------


> LogManager should use NullLogger as Fallback
> --------------------------------------------
>
>                 Key: VELOCITY-163
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-163
>             Project: Velocity
>          Issue Type: Bug
>          Components: Engine
>    Affects Versions: 1.3.1
>         Environment: Operating System: All
> Platform: All
>            Reporter: Jens Elkner
>         Assigned To: Velocity-Dev List
>
> To avoid unnecessary dependencies on avalon (which is IMHO not 
> ready for production use) and making velocity more stable,
> org/apache/velocity/runtime/log/LogManager should use an 
> "always available" LogSystem, i.e. AFAIK the NullLogger.
> IMHO, refusing to work because no known "LogSystem" is available,
> is not a very wise design decision...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org