We're in a catch-22. Curator 4.3's source cannot build against ZK 3.6.0 due to API changes. So, there's nothing we can do regarding that.
-JZ > On May 21, 2020, at 5:26 PM, Tamas Penzes <[email protected]> wrote: > > Hi All, > > After seeing Jordan's message to call people to test Curator I've tried to > build our whole stack together with Curator 5.0.0-snapshot (just to check > what fails). > As we use our own ZooKeeper version based on ZooKeeper 3.5.5 the given > ZooKeeper got replaced in Curator and the Curator build failed. I got the > following error during the build: > > [INFO] > /Users/tamaas/projects/curator/curator-framework/src/main/java/org/apache/curator/framework/imps/CuratorFrameworkImpl.java: > Recompile with -Xlint:deprecation for details. > [INFO] ------------------------------------------------------------- > [ERROR] COMPILATION ERROR : > [INFO] ------------------------------------------------------------- > [ERROR] > /Users/tamaas/projects/curator/curator-framework/src/main/java/org/apache/curator/framework/api/AddWatchBuilder.java:[21,28] > cannot find symbol > symbol: class AddWatchMode > location: package org.apache.zookeeper > > ... > > > The root cause is that ZOOKEEPER-1416 is only present in ZooKeeper 3.6.0+. > > Does Curator want to be compatible with ZooKeeper 3.5 only in runtime or we > should be able to build it against ZooKeeper 3.5.x versions too? > > Is there any way to recognise which ZooKeeper version we use runtime (to > raise an exception) or any feature flag to block these features or users > have to limit their use of Curator features (based on which ZooKeeper they > use) based on the documentation? > > Based on this updating Curator first and ZooKeeper afterwards won't work. > Does Curator 4.3.0 work with ZooKeeper 3.6.x? > > Thanks, Tamaas
