You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Rahul Akolkar (JIRA)" <ji...@apache.org> on 2009/01/05 21:09:44 UTC

[jira] Updated: (SCXML-92) Incorrect log level for entry/exit trace etc

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

Rahul Akolkar updated SCXML-92:
-------------------------------

    Fix Version/s: 1.0
                   0.10

This sounds like a good solution. Please go ahead and I'll try it out once its in SVN.

Setting fix versions to next releases from trunk and J6 branch.


> Incorrect log level for entry/exit trace etc
> --------------------------------------------
>
>                 Key: SCXML-92
>                 URL: https://issues.apache.org/jira/browse/SCXML-92
>             Project: Commons SCXML
>          Issue Type: Bug
>    Affects Versions: 0.9
>            Reporter: Sebb
>            Priority: Minor
>             Fix For: 0.10, 1.0
>
>
> Many of the classes use INFO level for what appear to be DEBUG level information.
> For example, SCXMLListener#onEntry() uses INFO level to log the state parameter. Such logs should be reduced to DEBUG level.

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