tag | 6bf1f569de707f01c5b8eefc2a050a2074b46afa | |
---|---|---|
tagger | Enrico Olivelli <eolivelli@localhost.localdomain> | Wed Oct 16 02:24:39 2019 +0200 |
object | c11b7e26bc554b8523dc929761dd28808913f091 |
ZooKeeper 3.5.6 release.
commit | c11b7e26bc554b8523dc929761dd28808913f091 | [log] [tgz] |
---|---|---|
author | Enrico Olivelli <eolivelli@localhost.localdomain> | Tue Oct 08 15:16:18 2019 +0200 |
committer | Andor Molnar <andor@apache.org> | Tue Oct 08 15:16:47 2019 +0200 |
tree | c2ba6cc8c2a4ceb5f5e5fa7167127ffe3d305a3d | |
parent | 3433841cb8e8ed1e1a3ef65e6e986aae3de55677 [diff] |
ZOOKEEPER-3563: Update Netty to 4.1.42.Final - fix license files Fix licence files not changed in 874aaf136ccda2759cc61f4c48ff9d15f6433e07 Author: Enrico Olivelli <eolivelli@localhost.localdomain> Reviewers: andor@apache.org Closes #1111 from eolivelli/fix/ZOOKEEPER-3563-netty-lic (cherry picked from commit 2dcb5e799ec02a2c6a6c7bad80c47169dc095271) Signed-off-by: Andor Molnar <andor@apache.org>
For the latest information about Apache ZooKeeper, please visit our website at:
and our wiki, at:
https://cwiki.apache.org/confluence/display/ZOOKEEPER
Either downloaded from https://zookeeper.apache.org/releases.html or found in zookeeper-assembly/target directory after building the project with maven.
apache-zookeeper-[version].tar.gz Contains all the source files which can be built by running: mvn clean install To generate an aggregated apidocs for zookeeper-server and zookeeper-jute: mvn javadoc:aggregate (generated files will be at target/site/apidocs) apache-zookeeper-[version]-bin.tar.gz Contains all the jar files required to run ZooKeeper Full documentation can also be found in the docs folder
As of version 3.5.5, the parent, zookeeper and zookeeper-jute artifacts are deployed to the central repository after the release is voted on and approved by the Apache ZooKeeper PMC:
https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/
If you are going to compile with Java 1.8, you should use a recent release at u211 or above.
We always welcome new contributors to the project! See How to Contribute for details on how to submit patch through pull request and our contribution workflow.