You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2011/06/30 11:00:30 UTC

[jira] [Updated] (ZOOKEEPER-1111) JMXEnv uses System.err instead of logging

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

Ivan Kelly updated ZOOKEEPER-1111:
----------------------------------

    Attachment: ZOOKEEPER-1111.diff

Patch is very simple. Simply replaces System.err with LOG.info. 

I neglected to mention that this only really shows up on hedwig, as zookeeper itself uses ant and ant's junit launcher hijacks System.err into the test log file. 

> JMXEnv uses System.err instead of logging
> -----------------------------------------
>
>                 Key: ZOOKEEPER-1111
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1111
>             Project: ZooKeeper
>          Issue Type: Bug
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 3.4.0
>
>         Attachments: ZOOKEEPER-1111.diff
>
>
> As stated in the title, org.apache.zookeeper.test.JMXEnv uses System.err.println to output traces. This makes for a lot of noise on the console when you run the tests. It has a logging object already, so it should use that instead.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira