[
https://issues.apache.org/jira/browse/ZOOKEEPER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616139#action_12616139
]
Benjamin Reed commented on ZOOKEEPER-83:
----------------------------------------
I completely agreed with the goals you are expressing. Having ZooKeeper in the
Maven repository is a good thing all the way around.
The problem I have is supporting two different build tools. Granted we have a
patch now, but going forward we would have to maintain (meaning fixing the
build scripts and running the tests) both. I think that one build tool makes
everyones life sane (er).
I'm not familiar with most projects, but Hadoop (who we are a subproject of)
doesn't use Maven. I talked to Owen about Hadoop using Maven and he mentioned
they were looking at Ivy. I also see that there are Maven ant tasks from the
Maven project that we can use. It seems to me that least disruptive way to get
into the Maven repository is to use either the ant tasks or Ivy.
Do you guys have an opinion on either of those two routes?
> 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.
