I'm puzzled, what are we supposed to fix here? Perhaps the correct fix is
to figure out what their TestZkClient is doing and provide a contrib that
works similarly and is kept up to date with versions.
On Wed, Nov 30, 2011 at 12:37 PM, Patrick Hunt <[EMAIL PROTECTED]> wrote:
> It's an unpublished api but we still might want to address this in
> 3.4.1/trunk to reduce downstream impact: