summaryrefslogtreecommitdiffstats
path: root/zookeeper-server/zookeeper-server-3.6.2
diff options
context:
space:
mode:
authorHarald Musum <musum@verizonmedia.com>2020-12-09 23:02:54 +0100
committerHarald Musum <musum@verizonmedia.com>2020-12-09 23:02:54 +0100
commit96803c16b15588532e9cd21611b104518fe0a0d7 (patch)
tree70efd0e9af9c7b4ef933d535272e5888e0912e01 /zookeeper-server/zookeeper-server-3.6.2
parentf3e2acd0df995ea17ddf016719d0f2ef33ef1427 (diff)
2 hacks to be able to use ZooKeeper server 3.6
Explicitly depend on io.dropwizard.metrics and org.xerial.snappy since they are used by metrics provider (even NullMetricsProvider) when bootstrapping ServerMetrics in zookeeper code and cannot be found when runnin in a container Do some class loadin trick to circumvent zookeeper itself loading a class with the threads current class loader, which does not work well in a container
Diffstat (limited to 'zookeeper-server/zookeeper-server-3.6.2')
-rw-r--r--zookeeper-server/zookeeper-server-3.6.2/pom.xml12
1 files changed, 12 insertions, 0 deletions
diff --git a/zookeeper-server/zookeeper-server-3.6.2/pom.xml b/zookeeper-server/zookeeper-server-3.6.2/pom.xml
index c479c84ac86..f6a8333a809 100644
--- a/zookeeper-server/zookeeper-server-3.6.2/pom.xml
+++ b/zookeeper-server/zookeeper-server-3.6.2/pom.xml
@@ -32,6 +32,18 @@
<version>1.7.5</version>
</dependency>
<dependency>
+ <groupId>io.dropwizard.metrics</groupId>
+ <artifactId>metrics-core</artifactId>
+ <scope>compile</scope>
+ <version>3.2.5</version>
+ </dependency>
+ <dependency>
+ <groupId>org.xerial.snappy</groupId>
+ <artifactId>snappy-java</artifactId>
+ <scope>compile</scope>
+ <version>1.1.7</version>
+ </dependency>
+ <dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<scope>test</scope>