The updated ZooKeeper client depends on Netty, but uses a newer version.
Prior to that version Netty switched its netty-all Maven coordinates from
being a super jar to being a pom that transitively depends on the other
Netty dependencies. This makes it possible for it to bring in a conflicting
version of Netty, resulting in two versions in the classpath. ZooKeeper
appears fine with our current Netty version, so excluding the transitive
dependencies seems the safest way to ensure no issues are caused by
upgrading Netty to match the ZooKeeper version.
The updated ZooKeeper client depends on Netty, but uses a newer version. Prior to that version Netty switched its netty-all Maven coordinates from being a super jar to being a pom that transitively depends on the other Netty dependencies. This makes it possible for it to bring in a conflicting version of Netty, resulting in two versions in the classpath. ZooKeeper appears fine with our current Netty version, so excluding the transitive dependencies seems the safest way to ensure no issues are caused by upgrading Netty to match the ZooKeeper version.