commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (SCXML-92) Incorrect log level for entry/exit trace etc
Date Mon, 05 Jan 2009 16:19:44 GMT

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


Mime
View raw message