You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2012/12/22 00:01:14 UTC
[jira] [Resolved] (TAP5-1888) Tapestry logging methods should use
T5.console instead of Tapestry.Logging
[ https://issues.apache.org/jira/browse/TAP5-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship resolved TAP5-1888.
----------------------------------------
Resolution: Won't Fix
Assignee: Howard M. Lewis Ship
This is no longer an issue in 5.4, and will not be revisited in 5.3.
> Tapestry logging methods should use T5.console instead of Tapestry.Logging
> --------------------------------------------------------------------------
>
> Key: TAP5-1888
> URL: https://issues.apache.org/jira/browse/TAP5-1888
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3.2, 5.3.3, 5.3.4, 5.3.5, 5.3.6
> Reporter: Jochen Kemnade
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Labels: javascript, logging, patch
> Attachments: 0001-use-T5.console-instead-of-Tapestry.Logging-compat-la.patch
>
>
> The client-side logging functions (Tapestry.debug and friends) should use the T5.console functions, not to the (deprecated) Tapestry.Logging compatibility layer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira