Patrick Hunt commented on ZOOKEEPER-83:

Regardless of whether this is a good idea or not we should consider whether 
it's a good idea _right now_. We are currently working towards 4 goals (in 
order or priority):

1) support/expand our user & contributor base
2) complete migration to ASF
3) 3.0 version of ZooKeeper
and just added recently
4) recipe implementation (which is a good thing IMO and also supports 1 above)

Given the current build system is functioning fine I personally think we should 
post-pone decisions like this and continue to work towards the goals listed 
above. There's more than enough work to go around w/o creating new.


I've added Roadmap and ProjectSuggestions pages to the ZooKeeper wiki. Pretty 
bare right now but I can tell you that tests (refactoring our current 
client/server test infrastructure in particular - see ZOOKEEPER-61) and 
documentation need alot of work. Don't hesitate to contact me or any of the 
other committers if you'd like to take on an existing Jira issue slated for 3.0 
or would like to be assigned something.

> Switch to using maven to build ZooKeeper
> ----------------------------------------
>                 Key: ZOOKEEPER-83
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-83
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: build
>            Reporter: Hiram Chirino
>            Assignee: Hiram Chirino
>         Attachments: zookeeper-mavened.tgz
> Maven is a great too for building java projects at the ASF.  It helps 
> standardize the build a bit since it's a convention oriented.
> It's dependency auto downloading would remove the need to store the 
> dependencies in svn, and it will handle many of the suggested ASF policies 
> like gpg signing of the releases and such.
> The ZooKeeper build is almost vanilla except for the jute compiler bits.  
> Things that would need to change are:
>  * re-organize the source tree a little so that it uses the maven directory 
> conventions
>  * seperate the jute bits out into seperate modules so that a maven plugin 
> can be with it

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to