commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (SCXML-92) Incorrect log level for entry/exit trace etc
Date Tue, 25 Nov 2008 20:31:44 GMT

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

Rahul Akolkar resolved SCXML-92.
--------------------------------

    Resolution: Won't Fix

There is nothing really incorrect about the log level. If anything, it reflects more on the
choices made that make development easier for a particular style. I prefer to run individual
tests in my IDE (and especially so when I add tests or when tests fail), and the additional
output to console about the progress of the state machine upto the point of failure is very
helpful. When I run the entire test suite, the output does not annoy me because I'm mostly
interested in overall success or failure rather than the nitty gritty of individual tests.
Seems like a matter of taste to me.

Also note that such copious output doesn't automatically appear on production boxes because
you actively choose to attach listeners you want (the tests use listeners that choose to log
at info).

Resolving as Won't Fix.


> 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
>
> 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.


Mime
View raw message