Нема описа

Tamas Penzes e92fdfefb8 ZOOKEEPER-3154: Update release process to use the MarkDown solution пре 6 година
bin faa7cec71f ZOOKEEPER-3032: MAVEN MIGRATION - move java server, client пре 6 година
conf 3819022566 ZOOKEEPER-1952 Default log directory and file name can be changed(nijel, Hari Krishna Dara via rakeshr) пре 10 година
docs faa7cec71f ZOOKEEPER-3032: MAVEN MIGRATION - move java server, client пре 6 година
zookeeper-client effa016c62 ZOOKEEPER-3106: Zookeeper client supports IPv6 address and document the "IPV6 feature" пре 6 година
zookeeper-common 6285f332a7 ZOOKEEPER-3159: Flaky: ClientRequestTimeoutTest.testClientRequestTimeout пре 6 година
zookeeper-contrib faa7cec71f ZOOKEEPER-3032: MAVEN MIGRATION - move java server, client пре 6 година
zookeeper-docs e92fdfefb8 ZOOKEEPER-3154: Update release process to use the MarkDown solution пре 6 година
zookeeper-it faa7cec71f ZOOKEEPER-3032: MAVEN MIGRATION - move java server, client пре 6 година
zookeeper-jute b7181d2c5a ZOOKEEPER-3080: MAVEN MIGRATION - Step 1.5 - move jute dir пре 7 година
zookeeper-recipes faa7cec71f ZOOKEEPER-3032: MAVEN MIGRATION - move java server, client пре 6 година
zookeeper-server ee250f1416 ZOOKEEPER-3161: Refactor QuorumPeerMainTest.java: move commonly used functions to base class пре 6 година
.gitattributes d94dcda0df ZOOKEEPER-1966. VS and line breaks (Orion Hodson via fpj) пре 11 година
.gitignore faa7cec71f ZOOKEEPER-3032: MAVEN MIGRATION - move java server, client пре 6 година
LICENSE.txt 47b8275402 Created notice and renamed the existing license/readme files. See ZOOKEEPER-45 пре 17 година
NOTICE.txt 7550dbcf01 ZOOKEEPER-1895. update all notice files, copyright, etc... with the new year - 2014 пре 11 година
README.md 86577c9d81 ZOOKEEPER-2880: Rename README.txt to README.md пре 8 година
README_packaging.txt 2ab0821db4 ZOOKEEPER-1604 remove rpm/deb/... packaging (cnauroth via phunt) пре 9 година
build.xml e92fdfefb8 ZOOKEEPER-3154: Update release process to use the MarkDown solution пре 6 година
ivy.xml fdde8b0064 ZOOKEEPER-1177: Add the memory optimized watch manager for concentrate watches scenario пре 6 година
ivysettings.xml 8d0154bcc2 ZOOKEEPER-2594: Use TLS for downloading artifacts during build (Olaf Flebbe via phunt) пре 8 година
pom.xml e92fdfefb8 ZOOKEEPER-3154: Update release process to use the MarkDown solution пре 6 година
zk-merge-pr.py d310d45bb9 ZOOKEEPER-2632: Add option to inform JIRA_PASSWORD at CLI prompt (Edward Ribeiro via phunt) пре 8 година

README.md

Apache ZooKeeper

alt text

For the latest information about Apache ZooKeeper, please visit our website at:

http://zookeeper.apache.org/

and our wiki, at:

https://cwiki.apache.org/confluence/display/ZOOKEEPER

Full documentation for this release can also be found in docs/index.html


Packaging/release artifacts

The release artifact contains the following jar file at the top level:

zookeeper-.jar - legacy jar file which contains all classes

                              and source files. Prior to version 3.3.0 this
                              was the only jar file available. It has the 
                              benefit of having the source included (for
                              debugging purposes) however is also larger as
                              a result

The release artifact contains the following jar files in "dist-maven" directory:

zookeeper-.jar - bin (binary) jar - contains only class (.class) files zookeeper--sources.jar - contains only src (.java) files zookeeper--javadoc.jar - contains only javadoc files

These bin/src/javadoc jars were added specifically to support Maven/Ivy which have the ability to pull these down automatically as part of your build process. The contents of the legacy jar and the bin + sources jars are the same.

As of version 3.3.0, the bin, sources and javadoc jars contained in the dist-maven directory 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/

Contributing

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.