[
https://issues.apache.org/jira/browse/ZOOKEEPER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615617#action_12615617
]
Flavio Paiva Junqueira commented on ZOOKEEPER-83:
-------------------------------------------------
I remember we had a discussion right when we moved ZooKeeper to sourceforge
about moving to maven, and we ended up agreeing not to do it. I'm happy to
retake the discussion, but as I don't fully understand all the implications of
moving to maven, it would be useful to me to understand what we gain and what
we lose by doing 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.
