[
https://issues.apache.org/jira/browse/ZOOKEEPER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616575#action_12616575
]
Hiram Chirino commented on ZOOKEEPER-83:
----------------------------------------
BTW there are lots of CI tools used at the ASF which DO support maven. But hey
if you like Hudson that's cool.
Can we at least merge the patch in so that the maven directory convention is
preserved and then we can delete the maven build files if you like. The ant
build can work with that structure just fine. If we do that then I can provide
folks who are interested in a maven build the pom files that just overlay onto
the project do they can use maven to build it.
So we both win. ZooKeeper only has 1 build system ant. Maven users also win
cause they can get some optional poms from me to build the project with. What
do you think?
> 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
> 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.
