GitHub user Randgalt opened a pull request:

    https://github.com/apache/curator/pull/233

    [CURATOR-427] Remove Classic connection handling

    Removed Classic connection handling as it's old, hard to maintain, forces 
us to run tests twice and isn't even what users expect.
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/curator CURATOR-427

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/curator/pull/233.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #233
    
----
commit abe2babd8300380299b6afb83986ed3741f1aa46
Author: randgalt <[email protected]>
Date:   2017-07-23T19:13:05Z

    back to 4.0.0-SNAPSHOT

commit ac0b489287256dd2413789957ed7c9a8478061ab
Author: randgalt <[email protected]>
Date:   2017-07-23T19:14:01Z

    doh back to 4.0.0-SNAPSHOT

commit 0cc62d64442e088bcaf9a8c43c14b28be12c87af
Author: randgalt <[email protected]>
Date:   2017-07-23T19:15:46Z

    [maven-release-plugin] prepare release apache-curator-4.0.0

commit 8d52ecbc5ae712a891c3567a0f12818aad3edddb
Author: randgalt <[email protected]>
Date:   2017-07-23T19:15:57Z

    [maven-release-plugin] prepare for next development iteration

commit 15eb063fa22569e797f850fb8d60a0949f52fbf5
Author: randgalt <[email protected]>
Date:   2017-07-24T04:56:20Z

    Removed Classic connection handling as it's old, hard to maintain, forces 
us to run tests twice and isn't even what users expect.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to