[ http://issues.apache.org/jira/browse/VELOCITY-165?page=all ]
Will Glass-Husain resolved VELOCITY-165:
----------------------------------------
Resolution: Invalid
Assign To: (was: Velocity-Dev List)
I'm going to mark this old bug invalid. This is really the responsibility of
your logging tool and/or app container. If you use log4j or commons log, set
this there. It's also easy to make a custom Velocity logger and direct
everything to System.err
> errors and stackTraces should go to System.err
> ----------------------------------------------
>
> Key: VELOCITY-165
> URL: http://issues.apache.org/jira/browse/VELOCITY-165
> Project: Velocity
> Type: Bug
> Components: Source
> Versions: 1.3.1
> Environment: Operating System: All
> Platform: All
> Reporter: Jens Elkner
> Priority: Minor
> Attachments: SimplePool.patch
>
> Actually it is annoying, to get the "transformed" output mixed with
> error messages.
> Unfortunately the log stuff is not used in a consequent manner:
> some methodes make use of System.out to report errors and StackTraces.
> Even if this is necessary, System.err should be used to avoid mixing
> results with more or less important error messages ...
--
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]
