[
https://issues.apache.org/jira/browse/CURATOR-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295640#comment-16295640
]
Martin Serrano commented on CURATOR-446:
----------------------------------------
Note, while curator is compatible with ZK 3.4.x at runtime, the test ZK classes
{{TestingZooKeeperMain}} and {{QuorumConfigBuilder}} (and perhaps others) use
3.5.x ZK APIs. This means ZK 3.5.x jars need to be in the classpath for
testing purposes. This makes it very difficult to use curator 4.0.0 if the you
want to work with 3.4.x. Since ZK 3.5.x has API incompatibilities with ZK
3.4.x, it is not viable to put ZK 3.5.x in the classpath just during testing.
IMO, this means it is not realistic to make the soft-compatibility claim with
3.4.x and the priority of this bug should be raised or the compatibility claim
removed.
> Compile error with tests using 4.0.0 and ZK 3.4.11
> --------------------------------------------------
>
> Key: CURATOR-446
> URL: https://issues.apache.org/jira/browse/CURATOR-446
> Project: Apache Curator
> Issue Type: Bug
> Components: Tests
> Affects Versions: 4.0.0
> Environment: gradle:
> compile('org.apache.zookeeper:zookeeper:3.4.11')
> testCompile ('org.apache.curator:curator-test:4.0.0') {
> exclude group: 'org.apache.zookeeper', module: 'zookeeper'
> }
> Reporter: Greg Moulliet
> Priority: Minor
>
> Attempting to start a test ZK gives the following error:
> Exception in thread "Thread-0" java.lang.NoSuchFieldError: configFileStr
> at
> org.apache.curator.test.QuorumConfigBuilder$1.<init>(QuorumConfigBuilder.java:142)
> at
> org.apache.curator.test.QuorumConfigBuilder.buildConfig(QuorumConfigBuilder.java:137)
> at
> org.apache.curator.test.TestingZooKeeperServer$1.run(TestingZooKeeperServer.java:157)
> at java.lang.Thread.run(Thread.java:745)
> Reverting back to 2.12.0 resolves the issue for me.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
