You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Michi Mutsuzaki (JIRA)" <ji...@apache.org> on 2014/04/23 22:42:15 UTC

[jira] [Resolved] (ZOOKEEPER-492) the tests should have their own log4j.properties

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

Michi Mutsuzaki resolved ZOOKEEPER-492.
---------------------------------------

    Resolution: Invalid

This is no longer a valid issue.

> the tests should have their own log4j.properties
> ------------------------------------------------
>
>                 Key: ZOOKEEPER-492
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-492
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: tests
>    Affects Versions: 3.1.1, 3.2.0
>            Reporter: Patrick Hunt
>            Priority: Minor
>             Fix For: 3.5.0
>
>
> the tests currently rely (QuorumPeerMainTest in particular) on conf/log4j.properties. if the user changes this file
> and then runs the tests the tests may fail. the tests should have their own log4j.properties maintained w/in the test
> directory itself, separate from conf/log4j.properties



--
This message was sent by Atlassian JIRA
(v6.2#6252)