Doug Cutting commented on ZOOKEEPER-83:

> Is that the only issue?

I think its fundamentally a cultural issue.  We have developers here who are 
familiar with Ant and have developed processes around Ant and are not 
frustrated with Ant and see no need to switch to a different build system.  
It's a bit like git versus svn: git may be better, but not enough folks yet 
feel that svn is a significant bottleneck, perhaps through ignorance.  I still 
use Emacs, despite folks telling me I should use an IDE.

If the majority of Zookeeper's community want to switch to Maven, I would 
certainly not oppose it.

> 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