You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Enrico Olivelli (Jira)" <ji...@apache.org> on 2020/02/04 09:45:00 UTC

[jira] [Resolved] (ZOOKEEPER-3703) Publish a Test-Jar from ZooKeeper Server

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

Enrico Olivelli resolved ZOOKEEPER-3703.
----------------------------------------
    Fix Version/s:     (was: 3.7.0)
                   3.5.7
       Resolution: Fixed

Issue resolved by pull request 1229
[https://github.com/apache/zookeeper/pull/1229]

> Publish a Test-Jar from ZooKeeper Server
> ----------------------------------------
>
>                 Key: ZOOKEEPER-3703
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3703
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: tests
>    Affects Versions: 3.5.6
>            Reporter: Jordan Zimmerman
>            Assignee: Jordan Zimmerman
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.6.0, 3.5.7
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> It would be very helpful to Apache Curator and others if ZooKeeper published its testing code as a Maven Test JAR. Curator, for example, could use it to improve its testing server to make it easier to inject error conditions without having to have forced time delays and other hacks.
> NOTE: if we move forward with gRPC (ZOOKEEPER-102) that would be in a new module and this would be required. So, might as well do it now.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)