[
https://issues.apache.org/jira/browse/TAPESTRY-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-1738.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.6
Assignee: Howard M. Lewis Ship
> Render debugging output is incredibly verbose, and should only be output at
> the TRACE (i.e. more vebose than DEBUG) logging level
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1738
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1738
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.6
>
>
> Currently if you enable debug output of your page class (i.e., to see the
> runtime code enhancement) you also get the incredibly verbose diagnostics for
> rendering of the page. That logging should be at trace, not debug. I
> believe commons-logging didn't properly offer a trace level (it merged
> verbose and debug together as debug).
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
