ZOOKEEPER-3033: MAVEN MIGRATION - Step 1.2 - create zk-recipes maven structure

Create the zk-recipes maven structure for the maven migration.
Tested the recipes build with the new directory structure.

Author: Norbert Kalmar <[email protected]>

Reviewers: [email protected]

Closes apache#564 from nkalmar/ZOOKEEPER-3033 and squashes the following commits:

c8c2e98 [Norbert Kalmar] ZOOKEEPER-3033 rename sub directories as well
d2b7f18 [Norbert Kalmar] ZOOKEEPER-3033 create zk-recipes maven structure

Author: nkalmar

build.xml

@@ -149,7 +149,7 @@ xmlns:cs="antlib:com.puppycrawl.tools.checkstyle.ant">
     <property name="dist.maven.dir" value="${dist.dir}/dist-maven"/>
 
     <property name="contrib.dir" value="${src.dir}/contrib"/>
-    <property name="recipes.dir" value="${src.dir}/recipes"/>
+    <property name="recipes.dir" value="${basedir}/zookeeper-recipes"/>
 
     <property name="ivy.version" value="2.4.0"/>
     <property name="ivy.url"

zookeeper-docs/src/documentation/content/xdocs/recipes.xml

@@ -283,7 +283,7 @@
     <note>
       <para>There now exists a Queue implementation in ZooKeeper
       recipes directory. This is distributed with the release --
-      src/recipes/queue directory of the release artifact.
+      zookeeper-recipes/zookeeper-recipes-queue directory of the release artifact.
       </para>
     </note>
 
@@ -312,7 +312,7 @@
     <note>
       <para>There now exists a Lock implementation in ZooKeeper
       recipes directory. This is distributed with the release --
-      src/recipes/lock directory of the release artifact.
+        zookeeper-recipes/zookeeper-recipes-lock directory of the release artifact.
       </para>
     </note>
 

src/recipes/README.txt zookeeper-recipes/README.txt

@@ -1,18 +1,19 @@
-1) This source directory contains various Zookeeper recipe implementations. 
+1) This source directory contains various Zookeeper recipe implementations.
 
-2) The recipe directory name should specify the name of the recipe you are implementing - eg. lock/.
+2) The recipe directory name should specify the name of the recipe you are implementing - eg. zookeeper-recipes-lock/.
 
 3) It would be great if you can provide both the java and c recipes for the zookeeper recipes.
-The c recipes go in to recipe-name/src/c and the java implementation goes into recipe-name/src/java.
+    C recipes go in to zookeeper-recipes/zookeeper-recipes-[recipe-name]/src/c
+    Java implementation goes into zookeeper-recipes/zookeeper-recipes-[recipe-name]/src/java.
 
 4) The recipes hold high standards like our zookeeper c/java libraries, so make sure that you include
 some unit testing with both the c and java recipe code.
 
 5) Also, please name your c client public methods as
 zkr_recipe-name_methodname
-(eg. zkr_lock_lock in lock/src/c)
+(eg. zkr_lock_lock in zookeeper-recipes-lock/src/c)
 
-6) The various recipes are in ../../docs/recipes.html or
+6) The various recipes are in ../docs/recipes.html or
 ../../docs/reciped.pdf. Also, this is not an exhaustive list by any chance.
 Zookeeper is used (and can be used) for more than what we have listed in the docs.
 
@@ -21,5 +22,5 @@ Zookeeper is used (and can be used) for more than what we have listed in the doc
 {top}/src/c/ are compiled. Run autoreconf -if;./configure; make. The libaries
 will be installed in {top}/src/c/.libs. 
 - run autoreconf if;./configure;make run-check 
-  in src/recipes/$recipename/src/c
+  in zookeeper-recipes/$recipename/src/c
 

src/recipes/build-recipes.xml zookeeper-recipes/build-recipes.xml

@@ -24,7 +24,7 @@
   <property name="name" value="${ant.project.name}"/>
   <property name="root" value="${basedir}"/>
 
-  <property name="zk.root" location="${root}/../../../"/>
+  <property name="zk.root" location="${root}/../../"/>
 
   <property name="src.dir"  location="${root}/src/java"/>
   <property name="src.test" location="${root}/src/test"/>