You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2008/11/25 11:07:44 UTC
[jira] Created: (SCXML-92) Incorrect log level for entry/exit trace
etc
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.
[jira] Resolved: (SCXML-92) Incorrect log level for entry/exit
trace etc
Posted by "Rahul Akolkar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SCXML-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rahul Akolkar resolved SCXML-92.
--------------------------------
Resolution: Fixed
I changed the XML formatting to match your comment above, I like that better and matches the style in the poms. Also works well for me so resolving as fixed -- thanks for fixing.
> 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.
[jira] Commented: (SCXML-92) Incorrect log level for entry/exit
trace etc
Posted by "Sebb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SCXML-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660906#action_12660906 ]
Sebb commented on SCXML-92:
---------------------------
Fixed in trunk:
URL: http://svn.apache.org/viewvc?rev=731692&view=rev
Log:
SCXML-92 - reduce logging when running full test suite
and J6:
URL: http://svn.apache.org/viewvc?rev=731693&view=rev
Log:
SCXML-92 - reduce logging when running full test suite
> 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.
[jira] Closed: (SCXML-92) Incorrect log level for entry/exit trace
etc
Posted by "Sebb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SCXML-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebb closed SCXML-92.
---------------------
> 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.
[jira] Updated: (SCXML-92) Incorrect log level for entry/exit trace
etc
Posted by "Rahul Akolkar (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Reopened: (SCXML-92) Incorrect log level for entry/exit
trace etc
Posted by "Sebb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SCXML-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebb reopened SCXML-92:
-----------------------
How about adding properties to the Surefire configuration to reduce the test output?
These would only apply when using "mvn test" - i.e. would not affect IDE testing output as far as I can tell.
I've tried the following and it works well for me:
{code}
<systemProperties>
<property>
<name>org.apache.commons.logging.Log</name>
<value>org.apache.commons.logging.impl.SimpleLog</value>
</property>
<property>
<name>org.apache.commons.logging.simplelog.defaultlog</name>
<value>warn</value>
</property>
</systemProperties>
{code}
> 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.
[jira] Resolved: (SCXML-92) Incorrect log level for entry/exit
trace etc
Posted by "Rahul Akolkar (JIRA)" <ji...@apache.org>.
[ 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.