[CURATOR-427] Remove ClassicConnectionHandling

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.0
• Fix Version/s: 4.0.0
• Component/s: Client, Framework
• Assignee: Jordan Zimmerman
• Reporter: Jordan Zimmerman
• Created: 24/Jul/17 04:41
• Updated: 26/Jul/17 13:55
• Resolved: 26/Jul/17 13:55

Description

ClassicConnectionHandlingPolicy was a stop-gap from Curator 2.x to Curator 3.x. Now that we're at 4.0 there's no reason to maintain it. It necessitates running the tests twice and is a headache to stay compatible. StandardConnectionHandlingPolicy is what users expect anyway.

Issue Links

• links to: GitHub Pull Request #233